bugfix: Corrected an issue in the Seata AT mode where, upon multiple … #6547
Conversation
This file contains 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
…modifications to the same record and encountering an exception during business execution, the rollback process would fail.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
…modifications to the same record and encountering an exception during business execution, the rollback process would fail.
Ⅰ. Describe what this PR did
When a business operation fails, Seata initiates a data rollback and concurrently checks if the data has been modified. If modifications are found, the rollback process may fail. In scenarios where the same record is updated multiple times, Seata's default sequential rollback approach can lead to rollback failures. By altering Seata's rollback strategy to perform rollbacks in reverse order—starting with the most recent modification and proceeding backwards—the issue can be resolved. This adjustment ensures that changes are undone from the latest to the earliest, effectively addressing the problem. (The fix involves storages such as DB, Redis, and file systems correctly returning branchIDs.)
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews