Bug 1255783
| Summary: | Server should enable writeSkew for some configurations by default | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Shay Matasaro <smatasar> | |
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> | |
| Status: | CLOSED UPSTREAM | QA Contact: | Martin Gencur <mgencur> | |
| Severity: | unspecified | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 6.5.0 | CC: | chuffman, jdg-bugs, onagano, vjuranek, wfink | |
| Target Milestone: | ER1 | |||
| Target Release: | 6.6.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
The server configuration did not allow users to specify write skew check option. This behavior could lead to inconsistencies on failure scenarios when using conditional operations with optimistic locking caches.
This issue is resolved as of Red Hat JBoss Data Grid 6.5.1, where write skew check is automatically enabled when using a combination of optimistic locking, synchronous cache mode, and <literal>REPEATABLE_READ</literal> isolation level.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1259355 (view as bug list) | Environment: | ||
| Last Closed: | 2025-02-10 03:48:05 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1254277, 1259355 | |||
Tristan Tarrant <ttarrant> updated the status of jira ISPN-5691 to Coding In Progress Tristan Tarrant <ttarrant> updated the status of jira ISPN-5691 to Open This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |
By default, optimistic locking caches do not enable write skew. This was already spotted in ISPN-3655. In an embedded environment, the user can always enable write skew in its configuration, but this cannot be enabled in server mode. Widlfly does enable write skew programmatically depending on the configuration: > hey, quick q: can you configure writeSkew on infinispan wildfly config? <pferraro> we always enable write skew for synchronous, optimistic, repeatable-read caches, and disable otherwise > pferraro: ah, you do it in the integration code? <pferraro> yes We need to be doing the same in server configuration, otherwise we run the risk of having issues with conditional operations under failure situations (see ISPN-2956)