Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Inline reroute with process of node join/master election #18938
In the past, we had the semantics where the very first cluster state a node processed after joining could not contain shard assignment to it. This was to make sure the node cleans up local / stale shard copies before receiving new ones that might confuse it. Since then a lot of work in this area, most notably the introduction of allocation ids and #17270 . This means we don't have to be careful and just reroute in the same cluster state change where we process the join, keeping things simple and following the same pattern we have in other places.
Jun 17, 2016
1 check passed
added a commit
this pull request
Jun 23, 2016
I reverted this one due to secondary problems with async shard fetch. I'm working on fixing those before re-committing this.
From the revert commit message: