You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Dan Smith (JIRA)" <ji...@apache.org> on 2018/09/27 20:33:00 UTC

[jira] [Updated] (GEODE-4928) Using a distributed lock to wrap a transaction will not prevent a CommitConflictException if members fail

     [ https://issues.apache.org/jira/browse/GEODE-4928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Smith updated GEODE-4928:
-----------------------------
    Summary: Using a distributed lock to wrap a transaction will not prevent a CommitConflictException if members fail  (was: DistributedLockService doesn't work as expected while the dlock grantor is initialized)

> Using a distributed lock to wrap a transaction will not prevent a CommitConflictException if members fail
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-4928
>                 URL: https://issues.apache.org/jira/browse/GEODE-4928
>             Project: Geode
>          Issue Type: New Feature
>          Components: distributed lock service
>            Reporter: Bruce Schuchardt
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> I wrote a function that obtained a dlock and then performed a transaction.  It always operates on the same dlock key and the same keys in my region.  That protects against getting a commit conflict exception BUT this sometimes fails if the JVM holding the lock crashes.  One of the functions appears to get the dlock okay but then its transaction fails when it goes to commit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)