You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/08 17:49:00 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16763786#comment-16763786 ]
ASF subversion and git services commented on GEODE-6379:
--------------------------------------------------------
Commit 9808685798bfb413597338f3c9491edfb64348fb in geode's branch refs/heads/feature/GEODE-6379 from eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=9808685 ]
GEODE-6379: track departed members to avoid processing in-flight lock request
> 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)