You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "Orcun Simsek (JIRA)" <ji...@apache.org> on 2013/11/27 04:27:35 UTC
[jira] [Updated] (CURATOR-79) InterProcessMutex doesn't clean up
after interrupt
[ https://issues.apache.org/jira/browse/CURATOR-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Orcun Simsek updated CURATOR-79:
--------------------------------
Description:
If the current thread is interrupted while acquiring the InterProcessMutex, a new node for the lock is created, InterruptException is thrown, and node is not deleted afterwards. Thus causing a deadlock.
Curator should check the Interrupted state, and do the proper clean up.
was:
If the current thread is interrupted while acquiring the InterProcessMutex, a new node for the lock is created, InterruptException is thrown, and node is not deleted afterwards. Thus causing a deadlock.
Curator should check the Interrupted state, and do the proper clean up.
> InterProcessMutex doesn't clean up after interrupt
> --------------------------------------------------
>
> Key: CURATOR-79
> URL: https://issues.apache.org/jira/browse/CURATOR-79
> Project: Apache Curator
> Issue Type: Bug
> Reporter: Orcun Simsek
> Assignee: Jordan Zimmerman
> Priority: Blocker
>
> If the current thread is interrupted while acquiring the InterProcessMutex, a new node for the lock is created, InterruptException is thrown, and node is not deleted afterwards. Thus causing a deadlock.
> Curator should check the Interrupted state, and do the proper clean up.
--
This message was sent by Atlassian JIRA
(v6.1#6144)