You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 7606fce
Browse filesBrowse the repository at this point in the historyBrowse files
branch-4.1: [fix](cloud) Invalidate version caches on visible commit retries (#67813) (#68650)
### What problem does this PR solve?
Issue Number: #67099
Related PR: #67813
Problem Summary: A retry after a lost cloud commit response can return a
VISIBLE transaction without version results. Invalidate the affected
table and partition version caches, and notify other FEs so subsequent
reads fetch current versions from the MetaService. This cherry-picks the
merged #67813 commit (`3dbe4d3ca53307f73db96eda23d4efc9f02963c5`) to
`branch-4.1`.
The conflict resolution keeps the branch-4.1 partition cache API, which
has no commit-TSO argument, and adapts the tests to its Java 8 and JUnit
4 setup. It preserves the source PR's cache invalidation epochs and
batch publication locks.
### Release note
Prevent stale reads and false commit failures after cloud commit
retries.
### Check List (For Author)
- Test
- [x] Unit Test: 51 passed (`CloudGlobalTransactionMgrTest`,
`CloudPartitionTest`, `OlapTableTest`, `VersionHelperTest`).
- [x] FE Checkstyle: 0 violations; `git diff --check` passed.
- [ ] Live cluster / SQL regression: not run.
- Behavior changed:
- [x] Yes. VISIBLE retries without versions invalidate local and peer
caches; subsequent reads fetch fresh versions without changing the
successful commit outcome.
- Does this need documentation?
- [x] No.
0 commit comments