cockroachdb / cockroachdb/cockroach
concurrency: consider consulting tscache during PUSH_ABORT
Open
A-kv-transactions
branch-master
C-bug
T-kv
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
**Describe the problem**
A PUSH_ABORT might be sent by a pusher who has an out-of-date view of the transactions write timestamp. For clarity when debugging, it might make sense to consult the tscache's timestamp marker to avoid writing a txn record at the old timestamp.
We don't think this is a correctness issue. Just might help with debugging.
Jira issue: CRDB-60668
Contributor guide
Assessment
This issue has not been assessed yet.