Boaz Leskes 4be94cdc95 revert - Inline reroute with process of node join/master election (#18938) ... There are secondary issues with async shard fetch going out to nodes before they have a cluster state published to them that need to be solved first. For example: - async fetch uses transport node action that resolves nodes based on the cluster state (but it's not yet exposed by ClusterService since we inline the reroute) - after disruption nodes will respond with an allocated shard (they didn't clean up their shards yet) which throws of decisions master side. - nodes deed the index meta data in question but they may not have if they didn't recieve the latest CS		2016-06-23 08:41:44 +02:00
..
src	revert - Inline reroute with process of node join/master election (#18938)	2016-06-23 08:41:44 +02:00
build.gradle	Upgrade joda-time to 2.9.4	2016-05-27 08:51:19 -04:00