Bug 841891
| Summary: | Potential tx lock leaks when nodes are added to the cluster | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Tristan Tarrant <ttarrant> |
| Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED UPSTREAM | QA Contact: | Nobody <nobody> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.0.0 | CC: | jdg-bugs, nobody |
| Target Milestone: | ER6 | ||
| Target Release: | 6.1.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
This situation only occurs during topology changes and results in certain keys remaining locked after a transaction is finished. This means that no other transaction is able to write to the given key while it is locked (though it can still be read).
As a workaround, one can enable transaction recovery and then use the JMX recovery hooks in order to cleanup the pending lock.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:20:20 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Tristan Tarrant
2012-07-20 13:48:35 UTC
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
CCFR from mmarkus
This situation only happens during topology changes and results in certain key remaining locked after a transaction is finished. This means that no other transaction would be able to write the given key as long as they are locked (would be able to read them though). ISPN-2137 contains a workaround for recovering from these situation. Adrian Nistor <anistor> made a comment on jira ISPN-2137 Integrated. ttarrant will add jira links as appropriate. VERIFIED for 6.1.0.ER6 I've taken test: LockCleanupStateTransferTest (+added it to 5.1.5.FINAL) and ran it for 5.1.5.FINAL - Failed 5.2.0.Beta6 - Passed Note: (the ER6 JAR was taken from MEAD repo - btw not md5sum-same as the JAR in jboss-datagrid-library-6.1.0.ER6.zip) JAR in jboss-datagrid-library-6.1.0.ER6.zip: b8de37f0bd621246585a4de5939c66de JAR in repo: a122144dac3b9d3e767389207bf6815a (I tested both JARs) The point of failure for 5.1.5.FINAL was here https://github.com/infinispan/infinispan/blob/master/core/src/test/java/org/infinispan/tx/LockCleanupStateTransferTest.java#L152 Which IMO correspondes to the failing scenario described in ISPN-2137 This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |