HDDS-6322. Fix Recon getting inccorrect sequenceNumber from OM #3090
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This bug was imported in HDDS-6215, the root cause is we used
dbUpdates.getData().size()to accumulate the sequenceNumber. But these two terms are different, a DBUpdates with data size of 10 could have a difference of sequenceNumber of 30 or more.The bug can be reproduced by adding the following configurations and running
TestReconWithOzoneManager.What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6322
How was this patch tested?
unit test.