[jira] [Updated] (GEODE-10250) The LockGrantor can grant a lock to a member that has left the distributed system
[ https://issues.apache.org/jira/browse/GEODE-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-10250: -- Labels: GeodeOperationAPI pull-request-available (was: pull-request-available) > The LockGrantor can grant a lock to a member that has left the distributed > system > - > > Key: GEODE-10250 > URL: https://issues.apache.org/jira/browse/GEODE-10250 > Project: Geode > Issue Type: Bug > Components: distributed lock service >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: GeodeOperationAPI, pull-request-available > > If a member requests a distributed lock and then leaves the distributed > system, the grantor may grant that request and leave itself in a state where > the lock has been granted but the member has left. > Here are the steps: > # The lock requesting server requests a lock > # The grantor server is delayed in granting that lock > # The lock requesting server shutsdown in the meantime > # The grantor server finally grants the lock after it has released all locks > and pending requests for the lock requesting server > # The lock requesting server receives the lock response but drops it since > the thread pool has been already shutdown -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10250) The LockGrantor can grant a lock to a member that has left the distributed system
[ https://issues.apache.org/jira/browse/GEODE-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anilkumar Gingade updated GEODE-10250: -- Labels: pull-request-available (was: needsTriage pull-request-available) > The LockGrantor can grant a lock to a member that has left the distributed > system > - > > Key: GEODE-10250 > URL: https://issues.apache.org/jira/browse/GEODE-10250 > Project: Geode > Issue Type: Bug > Components: distributed lock service >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: pull-request-available > > If a member requests a distributed lock and then leaves the distributed > system, the grantor may grant that request and leave itself in a state where > the lock has been granted but the member has left. > Here are the steps: > # The lock requesting server requests a lock > # The grantor server is delayed in granting that lock > # The lock requesting server shutsdown in the meantime > # The grantor server finally grants the lock after it has released all locks > and pending requests for the lock requesting server > # The lock requesting server receives the lock response but drops it since > the thread pool has been already shutdown -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10250) The LockGrantor can grant a lock to a member that has left the distributed system
[ https://issues.apache.org/jira/browse/GEODE-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated GEODE-10250: --- Labels: needsTriage pull-request-available (was: needsTriage) > The LockGrantor can grant a lock to a member that has left the distributed > system > - > > Key: GEODE-10250 > URL: https://issues.apache.org/jira/browse/GEODE-10250 > Project: Geode > Issue Type: Bug > Components: distributed lock service >Reporter: Barrett Oglesby >Assignee: Barrett Oglesby >Priority: Major > Labels: needsTriage, pull-request-available > > If a member requests a distributed lock and then leaves the distributed > system, the grantor may grant that request and leave itself in a state where > the lock has been granted but the member has left. > Here are the steps: > # The lock requesting server requests a lock > # The grantor server is delayed in granting that lock > # The lock requesting server shutsdown in the meantime > # The grantor server finally grants the lock after it has released all locks > and pending requests for the lock requesting server > # The lock requesting server receives the lock response but drops it since > the thread pool has been already shutdown -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (GEODE-10250) The LockGrantor can grant a lock to a member that has left the distributed system
[ https://issues.apache.org/jira/browse/GEODE-10250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Murmann updated GEODE-10250: -- Labels: needsTriage (was: ) > The LockGrantor can grant a lock to a member that has left the distributed > system > - > > Key: GEODE-10250 > URL: https://issues.apache.org/jira/browse/GEODE-10250 > Project: Geode > Issue Type: Bug > Components: distributed lock service >Reporter: Barrett Oglesby >Priority: Major > Labels: needsTriage > > If a member requests a distributed lock and then leaves the distributed > system, the grantor may grant that request and leave itself in a state where > the lock has been granted but the member has left. > Here are the steps: > # The lock requesting server requests a lock > # The grantor server is delayed in granting that lock > # The lock requesting server shutsdown in the meantime > # The grantor server finally grants the lock after it has released all locks > and pending requests for the lock requesting server > # The lock requesting server receives the lock response but drops it since > the thread pool has been already shutdown -- This message was sent by Atlassian Jira (v8.20.7#820007)