Skip to content

Conversation

@dnhatn
Copy link
Member

@dnhatn dnhatn commented Aug 1, 2019

Previously, if the metadata snapshot is empty (either no commit found or error), we won't compute the starting sequence number and use -2 to opt out the operation-based recovery. With #43463, we have a starting sequence number before reading the last commit. Thus, we need to reset it if we fail to snapshot the store.

Closes #45072

@dnhatn dnhatn added >bug :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source. labels Aug 1, 2019
@dnhatn dnhatn requested a review from ywelsch August 1, 2019 16:47
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

Copy link
Contributor

@ywelsch ywelsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dnhatn
Copy link
Member Author

dnhatn commented Aug 1, 2019

run elasticsearch-ci/2 (unrelated watcher test failure)

@dnhatn
Copy link
Member Author

dnhatn commented Aug 1, 2019

Thanks @ywelsch.

@dnhatn dnhatn merged commit 77720e8 into elastic:peer-recovery-retention-leases Aug 1, 2019
dnhatn added a commit that referenced this pull request Aug 1, 2019
Previously, if the metadata snapshot is empty (either no commit found or
error), we won't compute the starting sequence number and use -2 to opt
out the operation-based recovery. With #43463, we have a starting
sequence number before reading the last commit. Thus, we need to reset
it if we fail to snapshot the store.

Closes #45072
@dnhatn dnhatn deleted the reset-starting-seqno branch August 1, 2019 20:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Distributed Indexing/Recovery Anything around constructing a new shard, either from a local or a remote source.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants