[IOTDB-5706] Data inconsistency between IoT protocol replications#11727
Merged
OneSizeFitsQuorum merged 1 commit intoapache:masterfrom Dec 15, 2023
Merged
[IOTDB-5706] Data inconsistency between IoT protocol replications#11727OneSizeFitsQuorum merged 1 commit intoapache:masterfrom
OneSizeFitsQuorum merged 1 commit intoapache:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
The status code returned for handling BatchProcessException is
WRITE_PROCESS_ERROR, but this status code was not included in the retry judgment of IoT, so the batch that caused BatchProcessException did not retry, resulting in inconsistent data between IoT replications.To fix the problem, we add the status code
WRITE_PROCESS_ERRORin IoT Retry judgment.Besides, the atomicity issue of storage engine write operations can also lead to data inconsistency, which will be fixed in subsequent work.
Please see jira for details.