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

Force a new history uuid when force allocating a stale primary #26712

Closed
bleskes opened this issue Sep 19, 2017 · 1 comment
Closed

Force a new history uuid when force allocating a stale primary #26712

bleskes opened this issue Sep 19, 2017 · 1 comment
Assignees
@bleskes @dnhatn
Labels
:Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. >enhancement

Comments

@bleskes
Copy link
Contributor

bleskes commented Sep 19, 2017

This is a follow up to #26694 which didn't cover that edge case. The rationale is similar - it's unsafe to do ops based recoveries from those primaries
@bleskes bleskes self-assigned this Sep 19, 2017
@clintongormley clintongormley added :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. and removed :Sequence IDs labels Feb 14, 2018
@dnhatn dnhatn self-assigned this Mar 16, 2018
@colings86 colings86 added >enhancement :Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. labels Apr 24, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@colings86 colings86 removed the :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. label Apr 24, 2018
@elasticmachine elasticmachine mentioned this issue Aug 30, 2018
Closed
29 tasks
@dnhatn dnhatn mentioned this issue Sep 5, 2018
Merged
dnhatn added a commit that referenced this issue Sep 8, 2018
@dnhatn
Bootstrap a new history_uuid when force allocating a stale primary (#…
94e4cb6 
…33432)

This commit ensures that we bootstrap a new history_uuid when force
allocating a stale primary. A stale primary should never be the source
of an operation-based recovery to another shard which exists before the
forced-allocation.

Closes #26712
dnhatn added a commit that referenced this issue Sep 10, 2018
@dnhatn
Bootstrap a new history_uuid when force allocating a stale primary (#…
0f53972 
…33432)

This commit ensures that we bootstrap a new history_uuid when force
allocating a stale primary. A stale primary should never be the source
of an operation-based recovery to another shard which exists before the
forced-allocation.

Closes #26712
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bleskes bleskes

@dnhatn dnhatn

Labels
:Distributed Indexing/Distributed A catch all label for anything in the Distributed Area. Please avoid if you can. >enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@clintongormley @colings86 @bleskes @dnhatn @elasticmachine