{"push_id":939101443,"size":1,"distinct_size":1,"ref":"refs/heads/shard-state-action-channel-exceptions","head":"b5be988896d59fbbf92230cbd60e63652d2d173a","before":"6efc7012f5ae36d39c209108454a9e63a0b188fa","commits":[{"sha":"b5be988896d59fbbf92230cbd60e63652d2d173a","author":{"email":"68c46a606457643eab92053c1c05574abb26f861@tedor.me","name":"Jason Tedor"},"message":"Fix transport exceptions for shard state actions\n\nThis commit fixes an issue in the handling of TransportExceptions in\nShardStateAction. There were two cases not being handled correctly.\n - when the local node is shutting down, handlers will be notified with\n   a TransportException with a message starting \"transport stopped\"\n - when the remote node disconnects, handlers will be notified with a\n   NodeDisconnectedException\n\nIn both of these cases, the cause of the exception will be null and this\nwas incorrectly being handled. The first case can passed to the listener\nlike any other critical non-channel failure, and the second case can be\nhandled by modifying the logic for detecting master channel exceptions.","distinct":true,"url":"https://api.github.com/repos/jasontedor/elasticsearch/commits/b5be988896d59fbbf92230cbd60e63652d2d173a"}]}