You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Robert Lacroix (JIRA)" <ji...@apache.org> on 2015/04/15 05:06:59 UTC
[jira] [Assigned] (MESOS-1634) Calling stop on SchedulerDriver
leaves Zookeeper connection left behind
[ https://issues.apache.org/jira/browse/MESOS-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Lacroix reassigned MESOS-1634:
-------------------------------------
Assignee: Robert Lacroix
> Calling stop on SchedulerDriver leaves Zookeeper connection left behind
> -----------------------------------------------------------------------
>
> Key: MESOS-1634
> URL: https://issues.apache.org/jira/browse/MESOS-1634
> Project: Mesos
> Issue Type: Bug
> Components: framework
> Affects Versions: 0.18.0
> Reporter: Robert Lacroix
> Assignee: Robert Lacroix
>
> When calling stop on SchedulerDriver, the Zookeeper connection of ZooKeeperMasterDetector is not closed. This leaks connections to Zookeeper. We should properly close them when stop is called.
> {code}
> $ netstat -an | grep 2181 | grep tcp4 | grep ESTABLISHED
> 2
> 2014-07-23 17:46:53,840:26108(0x1246a8000):ZOO_INFO@check_events@1750: session establishment complete on server [127.0.0.1:2181], sessionId=0x14765c8e1a4000a, negotiated timeout=10000
> $ netstat -an | grep 2181 | grep tcp4 | grep ESTABLISHED
> 3
> I0723 17:48:57.354792 662249472 sched.cpp:730] Stopping framework '20140723-174036-16777343-5050-26021-0000'
> $ netstat -an | grep 2181 | grep tcp4 | grep ESTABLISHED
> 3
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)