You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/06/12 21:33:01 UTC

[jira] [Commented] (MESOS-1477) Deadlock when terminating ZooKeeperProcess

    [ https://issues.apache.org/jira/browse/MESOS-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029658#comment-14029658 ] 

Vinod Kone commented on MESOS-1477:
-----------------------------------

https://reviews.apache.org/r/22521/

> Deadlock when terminating ZooKeeperProcess
> ------------------------------------------
>
>                 Key: MESOS-1477
>                 URL: https://issues.apache.org/jira/browse/MESOS-1477
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Vinod Kone
>            Assignee: Vinod Kone
>
> (1) ZooKeeper callback in progress, calls ZooKeeperProcess::event.
> (2) ZooKeeperProcess::event calls ProcessWatcher::process.
> (3) ProcessWatcher::process calls zk->getSessionId().
> (4) This dispatches onto ZooKeeperProcess and blocks.
> If in between (1) and (4) there is a termination of the ZooKeeperProcess then (4) will block forever because the dispatch event will be dropped. This means that the zookeeper thread is blocked and zookeeper_close could block forever!
> This was introduced when the session id was added to all the dispatches inside WatcherProcess.



--
This message was sent by Atlassian JIRA
(v6.2#6252)