Bug 1255783 - Server should enable writeSkew for some configurations by default
Summary: Server should enable writeSkew for some configurations by default
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: 6.6.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1259355 1254277
TreeView+ depends on / blocked
 
Reported: 2015-08-21 14:32 UTC by Shay Matasaro
Modified: 2023-05-31 23:39 UTC (History)
6 users (show)

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.
Clone Of:
: 1259355 (view as bug list)
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-5691 0 Major Resolved Server should enable writeSkew for some configurations by default 2018-08-29 01:16:07 UTC

Description Shay Matasaro 2015-08-21 14:32:39 UTC
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)

Comment 2 JBoss JIRA Server 2015-08-21 19:27:07 UTC
Tristan Tarrant <ttarrant> updated the status of jira ISPN-5691 to Coding In Progress

Comment 3 JBoss JIRA Server 2015-08-21 19:27:12 UTC
Tristan Tarrant <ttarrant> updated the status of jira ISPN-5691 to Open


Note You need to log in before you can comment on or make changes to this bug.