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

Client transaction timeout makes transaction not able to rollback #8483

Closed
gurbuzali opened this issue Jun 30, 2016 · 0 comments

Comments

Projects
None yet
1 participant
@gurbuzali
Copy link
Member

commented Jun 30, 2016

Commit failure on clients sets the transaction state to ROLLING_BACK, which makes the transaction non-rollbackable. This is not a problem for lock-based data structures (map, multimap) but it is problematic for collections. Since Hazelcast does not have an auto-release the resources for collections yet (planned for 3.8) one should call rollback explicitly upon commit failure in order to release resources.

Please see https://groups.google.com/d/msgid/hazelcast/26611d6a-4c00-4fac-91eb-0803bdb77cf6%40googlegroups.com?utm_medium=email&utm_source=footer

@gurbuzali gurbuzali added this to the 3.7 milestone Jun 30, 2016

@gurbuzali gurbuzali self-assigned this Jun 30, 2016

gurbuzali added a commit to gurbuzali/hazelcast that referenced this issue Jun 30, 2016

gurbuzali added a commit to gurbuzali/hazelcast that referenced this issue Jul 19, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.