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 還沒有評估資料。