Automated transaction recovery
Abierto
component: Persistence
feature
scaling / performance
- Lenguaje dominante
- Scala
- Estrellas
- 667
- Forks
- 155
- Merge medio
- 3 d 6 h
- PR fusionados (30 d)
- 4
Descripción
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?
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.