Skip to content

Relax maxSeqNoOfUpdates assertion in FollowingEngine #47188

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

Merged
merged 3 commits into from
Sep 27, 2019

Conversation

dnhatn
Copy link
Member

@dnhatn dnhatn commented Sep 27, 2019

We disable MSU optimization if the local checkpoint is smaller than max_seq_no_of_updates. Hence, we need to relax the MSU assertion in FollowingEngine for that scenario. Suppose the leader has three operations: index-0, delete-1, and index-2 for the same doc Id. MSU on the leader is 1 as index-2 is an append. If the follower applies index-0 then index-2, then the assertion is violated.

Closes #47137

@dnhatn dnhatn added >bug :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features v8.0.0 v7.5.0 v7.4.1 v7.3.3 labels Sep 27, 2019
@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.

2 nits, looking good o.w.

@dnhatn
Copy link
Member Author

dnhatn commented Sep 27, 2019

Thanks @ywelsch.

@dnhatn dnhatn merged commit fbeb5a3 into elastic:master Sep 27, 2019
@dnhatn dnhatn deleted the ccr-msu branch September 27, 2019 15:13
dnhatn added a commit that referenced this pull request Sep 27, 2019
We disable MSU optimization if the local checkpoint is smaller than
max_seq_no_of_updates. Hence, we need to relax the MSU assertion in
FollowingEngine for that scenario. Suppose the leader has three
operations: index-0, delete-1, and index-2 for the same doc Id. MSU on
the leader is 1 as index-2 is an append. If the follower applies index-0
then index-2, then the assertion is violated.

Closes #47137
dnhatn added a commit that referenced this pull request Sep 27, 2019
We disable MSU optimization if the local checkpoint is smaller than
max_seq_no_of_updates. Hence, we need to relax the MSU assertion in
FollowingEngine for that scenario. Suppose the leader has three
operations: index-0, delete-1, and index-2 for the same doc Id. MSU on
the leader is 1 as index-2 is an append. If the follower applies index-0
then index-2, then the assertion is violated.

Closes #47137
dnhatn added a commit that referenced this pull request Sep 27, 2019
We disable MSU optimization if the local checkpoint is smaller than
max_seq_no_of_updates. Hence, we need to relax the MSU assertion in
FollowingEngine for that scenario. Suppose the leader has three
operations: index-0, delete-1, and index-2 for the same doc Id. MSU on
the leader is 1 as index-2 is an append. If the follower applies index-0
then index-2, then the assertion is violated.

Closes #47137
@tomcallahan tomcallahan removed the :Distributed Indexing/Engine Anything around managing Lucene and the Translog in an open shard. label Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>bug :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features v7.3.3 v7.4.1 v7.5.0 v8.0.0-alpha1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

FollowerFailOverIT testFailOverOnFollower & testAddNewReplicasOnFollower failure on CI
5 participants