-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility issue about multi Group TSO #6142
Comments
In keyspace scenario, there is a globally unique GC Worker to calculate the globally unique GC safepoint.
But if TSO in differrent group, multiple timelines will be created. Subsequent plan: the calculation of GC safepoint will be separated by keyspace,but the design discussion and code review may take more time. |
There is another problem: |
native_br also needs to get the global min ts. |
ref #6142 Signed-off-by: Ryan Leung <rleungx@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ref #6142 Signed-off-by: Ryan Leung <rleungx@gmail.com>
ref tikv#6142 Signed-off-by: Ryan Leung <rleungx@gmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
ref tikv#6142 Signed-off-by: Ryan Leung <rleungx@gmail.com>
Compatibility issue about Group TSO
ref #5895
MaxTS
Problem
Async Commit use max_ts to commit. The problem is, if multi group tso is used with async commit/1pc enabled, the
commit_ts
calculation becomes complicated. We can't record only onemax_ts
any more. For example, in this case:Commit k2 from TSO Group2
Resolve TS
the resolve ts formula:
Problem
If there is no locks, it maybe wrong update the resolved ts, fix with:
The text was updated successfully, but these errors were encountered: