antidote
antidote copied to clipboard
AntidoteDB
Un-commited/aborted transactions live forever
When a client application using Antidote crashes or has incorrect transaction handling, some or even many transactions can stay open. These transactions are never forcefully aborted by Antidote. This can potentially leave many txn-coordinator-fsms running forever.
For a database that should be deployed as a long-running system, this behavior is unacceptable. Transactions, that are not used anymore (receive no read or update requests) should be aborted after a fixed timeout. In my opinion, a timeout of say 5 minutes should be acceptable for most applications.
Just set a timer in the FSM that fires, and without X amount of activity terminate the FSM, no?
Make X a parameter of the deployment.
On Wed, Sep 6, 2017 at 11:21 AM, Christopher S. Meiklejohn < [email protected]> wrote:
Just set a timer in the FSM that fires, and without X amount of activity terminate the FSM, no?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SyncFree/antidote/issues/315#issuecomment-327441511, or mute the thread https://github.com/notifications/unsubscribe-auth/AJZR8oIYLUgZmVVNZc32WTEO8C9nm8Lgks5sfnIqgaJpZM4PNFWN .
