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

Sync up snapshot shard status on a master restart #11450

Merged
merged 1 commit into from Jun 3, 2015
Merged

Sync up snapshot shard status on a master restart #11450

merged 1 commit into from Jun 3, 2015

Commits on Jun 3, 2015

  1. Snapshot/Restore: sync up snapshot shard status on a master restart 

    When a snapshot operation on a particular shard finishes, the data node where this shard resides sends an update shard status request to the master node to indicate that the operation on the shard is done. When the master node receives the command it queues cluster state update task and acknowledges the receipt of the command to the data node.

The update snapshot shard status tasks have relatively low priority, so during cluster instability they tend to get stuck at the end of the queue. If the master node gets restarted before processing these tasks the information about the shards can be lost and the new master assumes that they are still in process while the data node thinks that these shards are already done.

 This commit add a retry mechanism that checks compares cluster state of a newly elected master and the current state of snapshot shards and updates the cluster state on the master again if needed.

Closes elastic#11314
    @imotov
    imotov committed Jun 3, 2015
    Configuration menu
    Copy the full SHA
    f0e6add View commit details
    Browse the repository at this point in the history