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 2013/02/15 01:21:13 UTC
[jira] [Commented] (MESOS-351) Master detector should not block on
zookeeper 'get' method
[ https://issues.apache.org/jira/browse/MESOS-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13578834#comment-13578834 ]
Vinod Kone commented on MESOS-351:
----------------------------------
gdb stack trace of the slave showing that the slave has some threads blocked on zookeeper code.
Thread 3 (Thread 0x4dd4f940 (LWP 2739)):
#0 0x00007f82b72c1186 in poll () from /lib64/libc.so.6
#1 0x00007f82b928f1a1 in do_io (v=<value optimized out>) at src/mt_adaptor.c:299
#2 0x00007f82b86cd73d in start_thread () from /lib64/libpthread.so.0
#3 0x00007f82b72c9f6d in clone () from /lib64/libc.so.6
Thread 2 (Thread 0x4e550940 (LWP 2740)):
#0 0x00007f82b86d1ee9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1 0x00007f82b928ef8b in do_completion (v=<value optimized out>) at src/mt_adaptor.c:330
#2 0x00007f82b86cd73d in start_thread () from /lib64/libpthread.so.0
#3 0x00007f82b72c9f6d in clone () from /lib64/libc.so.6
> Master detector should not block on zookeeper 'get' method
> ----------------------------------------------------------
>
> Key: MESOS-351
> URL: https://issues.apache.org/jira/browse/MESOS-351
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
>
> Currently, the master detector code calls zk->get() in its detectMaster() method. Under the covers, we call zoo_aget(...., callback,....) and block till the callback is called.
> At Twitter, we encountered a situation where zk->get() got blocked because the callback was never called by the underlying zookeeper library. Even if a watch expired indicating session expired, the detector would not process it because it is blocked in detectMaster().
> I will add some data below.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira