sig-transaction icon indicating copy to clipboard operation
sig-transaction copied to clipboard

Resources for the transaction SIG

Results 20 sig-transaction issues
Sort by recently updated
recently updated
newest added

Currently the green-gc is [disabled](https://github.com/pingcap/tidb/pull/22533) by default as it still has some corener cases or [issues](https://github.com/tikv/tikv/issues/8184) to solve. As the hibernate region is default [enabled](https://github.com/tikv/tikv/pull/9735) just on the master branch,...

Now the `min_commit_ts` of async commit transactions cannot be advanced like the legacy transactions. So if our read timestamp is larger than the `min_commit_ts` of an async-commit lock, we can...

T-async-commit
discussion

I fell our **unit** tests in TiKV somehow not satisfing. For example when reviewing [tikv#9514](https://github.com/tikv/tikv/pull/9514), which changed the **rollback collapse logic**, I found it breaked some test cases in **`mvcc::reader`**....

Async commit and 1PC are fundamental changes to the transaction protocol in TiDB. There will be new kinds of locks that need to be handled in new ways. Therefore, it...

Previously we found that schema version checking might be a problem. Later we think it can be solved if we define a transaction to be committed iff all its keys...

T-async-commit

It is likely we need to provide a solution for downgrading from TiKV 5.0 to 4.0. Here is the doc about handling async commit.

1. Green GC is not compatible with async commit if async apply is enabled: A lock isn't applied and the transaction may be committed. 2. TBD

Signed-off-by: MyonKeminta This PR adds a draft document for single region 1PC. This PR is also expected to be the place to do related discussions.

## Background We are going to finish async commit in 5.0, and there's going to be another important feature in 5.0: Local/Global transaction in cross DC deployment. In that feature,...

T-async-commit