Automated transaction recovery
未关闭
component: Persistence
feature
scaling / performance
- 主要语言
- Scala
- 星标
- 667
- 派生
- 155
- 平均合并
- 3 天 6 小时
- 30 天内合并 PR
- 4
描述
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?
贡献指南
这个仓库没有索引到贡献指南
评估
这个 Issue 还没有评估数据。