Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reroute after node join is processed #11960

Closed
wants to merge 1 commit into from
Closed

Reroute after node join is processed #11960

wants to merge 1 commit into from

Commits on Jun 30, 2015

  1. Discovery: reroute after node join is processed 

    elastic#11776 has simplified our rerouting logic by removing a scheduled background reroute in favor of an explicit reroute during the cluster state processing of a node join (the only place where we didn't do it explicitly). While that change is conceptually good, it change semantics a bit in two ways:

 - shard listing actions underpinning shard allocation do not have access to that new node yet (causing errors during shard allocation see elastic#11923
 - the very first cluster state published to a node already has shard assignments to it. This surfaced other issues we are working to fix separately

 This commit changes the reroute to be done post processing the initial join cluster state to side step these issues while we work on a longer term solution.
    @bleskes
    bleskes committed Jun 30, 2015
    Copy the full SHA
    e353526 View commit details
    Browse the repository at this point in the history