{"push_id":679535129,"size":1,"distinct_size":1,"ref":"refs/heads/1.x","head":"5fa95206fdaf611ab414c24ce5616c3d3b2ffccc","before":"dedbe528d5da95fdb6cccd1d0483aa0ca2c07563","commits":[{"sha":"5fa95206fdaf611ab414c24ce5616c3d3b2ffccc","author":{"email":"07214fe5dc19164a587acf4cfa1dc6b83a5ba1eb@gmail.com","name":"Shay Banon"},"message":"Reduce cluster update reroutes with async fetch\nWhen using async fetch, we can end up with cluster updates and reroutes based on teh number of shards. While not disastrous we can optimize it, since a single reroute is enough to apply to all the async fetch results that arrived during that time.","distinct":true,"url":"https://api.github.com/repos/elastic/elasticsearch/commits/5fa95206fdaf611ab414c24ce5616c3d3b2ffccc"}]}