Automated transaction recovery
Open
component: Persistence
feature
scaling / performance
- Dominant language
- Scala
- Stars
- 667
- Forks
- 155
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 4
Description
In rare cases when a transaction was broken and didn't rollback properly (network partitioning between shards, sudden coordinator crash etc), another transaction has to be able to take up on where the previous one left off.
Possible solutions:
1. Clean the previous transaction assets and start over.
2. Overwrite the previous transaction data.
Challenges:
1. How to distinguish between abandoned transaction and a long-running transaction in a distributed environment?
2. How to kill stuck transaction?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.