[jboss-jira] [JBoss JIRA] (WFLY-6096) ISPN-5876 changes need to be configurable

Stephen Fikes (JIRA) issues at jboss.org
Fri Jan 29 16:34:00 EST 2016


     [ https://issues.jboss.org/browse/WFLY-6096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Fikes updated WFLY-6096:
--------------------------------
    Component/s: Clustering
                     (was: ConfigAdmin)


> ISPN-5876 changes need to be configurable
> -----------------------------------------
>
>                 Key: WFLY-6096
>                 URL: https://issues.jboss.org/browse/WFLY-6096
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering
>            Reporter: Stephen Fikes
>            Assignee: Thomas Diesler
>
> When Infinispan 8.1 is incorporated in WildFly (WFLY-6094), the changes added as part of ISPN-5876 should be made non-default.
> For the databases that default to read blocking on modified rows (e.g. SQLServer) and for applications which can be designed to support pessimistic locking for all reads, the changes reduce the level of data integrity that can be guaranteed.
> As discussed in ISPN-5876, for databases which do not default to read blocking on modified rows or applications which cannot tolerate the cost of pessimistic locking, the changes address the case where stale data may be loaded and retained until explicitly evicted or timed out.
> Though the second case _may_ be the more common, it seems like the default should be to not reduce the integrity guarantee.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list