You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Eric Shu (JIRA)" <ji...@apache.org> on 2019/02/07 22:19:00 UTC

[jira] [Updated] (GEODE-6379) There is a race that transaction lock could be held for a departed member and causes no other transactions can operate on the key due to commit conflict

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

Eric Shu updated GEODE-6379:
----------------------------
    Affects Version/s: 1.1.0

> There is a race that transaction lock could be held for a departed member and causes no other transactions can operate on the key due to commit conflict
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-6379
>                 URL: https://issues.apache.org/jira/browse/GEODE-6379
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>    Affects Versions: 1.1.0
>            Reporter: Eric Shu
>            Assignee: Eric Shu
>            Priority: Major
>
> Currently, all transactional distributed lock held by a departed member will be released during member departed event. However, there is a race that a thread could execute an in-flight lock request after above mentioned event. This will cause some keys being locked but no one would release these locks - blocking further operations on the keys by other transactions.



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