[
https://issues.apache.org/jira/browse/GEODE-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16778683#comment-16778683
]
ASF subversion and git services commented on GEODE-6379:
--------------------------------------------------------
Commit 8ac449fd14c6d61498770f0039c5a4179d45c8ca in geode's branch
refs/heads/develop from pivotal-eshu
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=8ac449f ]
GEODE-6379: track departed members to avoid processing in-flight lock request
(#3176)
> 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
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> 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)
