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

Primary replica resync should not send ops without seqno #40881

Merged
merged 1 commit into from
Apr 5, 2019

Conversation

dnhatn
Copy link
Member

@dnhatn dnhatn commented Apr 5, 2019

Primary-replica resync in a mixed-cluster between 6.x and 5.6 can send
operations without sequence number to a replica which already processed
operations with sequence number. This leads to the failure of that
replica for we trip the sequence number assertion when writing resync
operations without sequence number to translog.

Backport of #40433

Primary-replica resync in a mixed-cluster between 6.x and 5.6 can send
operations without sequence number to a replica which already processed
operations with sequence number. This leads to the failure of that
replica for we trip the sequence number assertion when writing resync
operations without sequence number to translog.
@dnhatn dnhatn added the backport label Apr 5, 2019
@dnhatn dnhatn merged commit ca99c27 into elastic:6.7 Apr 5, 2019
@dnhatn dnhatn deleted the resync-ops-67 branch April 5, 2019 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant