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.

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

Unassigned shards after restore #8224

Closed
abaxanean opened this issue Oct 24, 2014 · 0 comments · Fixed by #8341
Closed

Unassigned shards after restore #8224

abaxanean opened this issue Oct 24, 2014 · 0 comments · Fixed by #8341
Assignees
Labels
>bug :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs

Comments

@abaxanean
Copy link

ES 1.3.3

  1. Have two nodes that form a cluster (one shard per index, no replicas).
  2. Insert some documents (multiple indices).
  3. Put repository, backup the cluster (global state = true, partial = false ).
  4. Stop both nodes.
  5. Delete the data folder of one of the nodes (path.data).
  6. Start the two nodes (the cluster has red status).
  7. Close all indices
  8. Put repository, restore (global state = true, partial = false).

Observed : Half of the shards remain unassigned.

Note : If deleting data folders of both nodes (on step 5), after restore everything is ok.

@imotov imotov added :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs >bug labels Nov 2, 2014
imotov added a commit to imotov/elasticsearch that referenced this issue Nov 18, 2014
…e in the cluster

Fixes the issue with restoring of an index that had only some of its primary shards allocated before it was closed.

Fixes elastic#8224
imotov added a commit that referenced this issue Nov 18, 2014
…e in the cluster

Fixes the issue with restoring of an index that had only some of its primary shards allocated before it was closed.

Fixes #8224
imotov added a commit that referenced this issue Nov 18, 2014
…e in the cluster

Fixes the issue with restoring of an index that had only some of its primary shards allocated before it was closed.

Fixes #8224
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
…e in the cluster

Fixes the issue with restoring of an index that had only some of its primary shards allocated before it was closed.

Fixes elastic#8224
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Distributed/Snapshot/Restore Anything directly related to the `_snapshot/*` APIs
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants