{"push_id":940903365,"size":1,"distinct_size":1,"ref":"refs/heads/validate-shard-failure-requests","head":"fefaa0dfa3fe33233d02720b03b43692af42863e","before":"10a23630125484fcb02b2de025997da99bb9cb65","commits":[{"sha":"fefaa0dfa3fe33233d02720b03b43692af42863e","author":{"email":"68c46a606457643eab92053c1c05574abb26f861@tedor.me","name":"Jason Tedor"},"message":"Shard failure requests for non-existent shards\n\nThis commit adds handling on the master side for shard failure requests\nfor shards that do not exist at the time that they are processed on the\nmaster node (whether it be from errant requests, duplicate requests, or\nboth the primary and replica notifying the master of a shard\nfailure). With this change is a refactoring of the\nShardStateAction.Listener into separate interfaces for shard failure\nrequests and shard started requests. Separating these interfaces permits\nus to add an onShardNotFound notification to the shard failure listener\nfor clarity on one of the possible outcomes of a shard failure request.","distinct":true,"url":"https://api.github.com/repos/jasontedor/elasticsearch/commits/fefaa0dfa3fe33233d02720b03b43692af42863e"}]}