Automated transaction recovery
Aberta
component: Persistence
feature
scaling / performance
- Linguagem predominante
- Scala
- Estrelas
- 667
- Forks
- 155
- Merge médio
- 3d 6h
- PRs com merge (30d)
- 4
Descrição
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?
Guia de contribuição
Nenhum guia de contribuição indexado para este repositório
Avaliação
Esta issue ainda não foi avaliada.