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 8c55eb0
Browse filesBrowse the repository at this point in the historyBrowse files
### What problem does this PR solve?
Issue Number: None
Related PR: apache#67181, apache#67594
Problem Summary: The commit TSO fence check lacked request-level and Meta Service configuration gates, its error name was unclear, the fence key was unavailable through Meta Service HTTP KV tooling, and the persisted window time did not state its unit. Add both fence-check gates to every Cloud commit path, expose the fence key to HTTP encode/get/set, rename the stale TSO error, and clarify the FE tracker and durable-state names.
### Release note
Cloud commit TSO fence checks can be controlled by the request and the mutable Meta Service configuration. Rejected stale commit TSOs now use TXN_COMMIT_TSO_EXPIRED.
### Check List (For Author)
- Test: Unit Test
- Targeted FE unit tests: 108 passed
- Cloud MetaService TSO fence test: passed
- Cloud HTTP encode/get/set tests: 11 passed
- Full ./build.sh -j32: passed
- Cloud clang-tidy on changed lines: passed
- Behavior changed: Yes. Commit TSO fencing requires both request and Meta Service gates, and the stale TSO error was renamed.
- Does this need documentation: No
0 commit comments