Automated transaction recovery
Aperta
component: Persistence
feature
scaling / performance
- Lingua principale
- Scala
- Stelle
- 667
- Fork
- 155
- Merge medio
- 3g 6h
- PR unite (30g)
- 4
Descrizione
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?
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Valutazione
Questa issue non è ancora stata valutata.