Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Un-commited/aborted transactions live forever #315

Open
mweberUKL opened this issue Sep 5, 2017 · 3 comments
Open

Un-commited/aborted transactions live forever #315

mweberUKL opened this issue Sep 5, 2017 · 3 comments
Assignees
Labels
bug good first issue Issues that can probably be solved by people new to the Antidote codebase.

Comments

@mweberUKL
Copy link
Contributor

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.

@cmeiklejohn
Copy link
Contributor

Just set a timer in the FSM that fires, and without X amount of activity terminate the FSM, no?

@preguica
Copy link

preguica commented Sep 6, 2017 via email

@cmeiklejohn
Copy link
Contributor

application:get_env

@bieniusa bieniusa self-assigned this Jul 26, 2019
@peterzeller peterzeller added the good first issue Issues that can probably be solved by people new to the Antidote codebase. label Oct 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug good first issue Issues that can probably be solved by people new to the Antidote codebase.
Projects
None yet
Development

No branches or pull requests

5 participants