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

Do not use versions to optimize cluster state copying for a first update from a new master #6466

Closed
wants to merge 2 commits into from
Closed

Do not use versions to optimize cluster state copying for a first update from a new master #6466

wants to merge 2 commits into from

Commits on Jun 11, 2014

  1. [Discovery] do not use versions to optimize cluster state copying for… 

    … a first update from a new master

We have an optimization which compares routing/meta data version of cluster states and tries to reuse the current object if the versions are equal. This can cause rare failures during recovery from a minimum_master_node breach when using the "new light rejoin" mechanism and simulated network disconnects. This happens where the current master updates it's state, doesn't manage to broadcast it to other nodes due to the disconnect and then steps down. The new master will start with a previous version and continue to update it. When the old master rejoins, the versions of it's state can equal but the content is different.
    @bleskes
    bleskes committed Jun 11, 2014
    Configuration menu
    Copy the full SHA
    05a14bd View commit details
    Browse the repository at this point in the history

  2. added randomization between responsive/unresponsive network disconnects

    @bleskes
    bleskes committed Jun 11, 2014
    Configuration menu
    Copy the full SHA
    647dad9 View commit details
    Browse the repository at this point in the history