You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrei Sekretenko (Jira)" <ji...@apache.org> on 2020/02/13 12:41:00 UTC
[jira] [Commented] (MESOS-10097) After HTTP framework disconnects,
heartbeater idle-loops instead of being deleted.
[ https://issues.apache.org/jira/browse/MESOS-10097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17036186#comment-17036186 ]
Andrei Sekretenko commented on MESOS-10097:
-------------------------------------------
https://reviews.apache.org/r/72130/
> After HTTP framework disconnects, heartbeater idle-loops instead of being deleted.
> ----------------------------------------------------------------------------------
>
> Key: MESOS-10097
> URL: https://issues.apache.org/jira/browse/MESOS-10097
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 1.5.3, 1.6.2, 1.7.2, 1.8.1, 1.9.0, 1.10
> Reporter: Andrei Sekretenko
> Assignee: Andrei Sekretenko
> Priority: Minor
>
> In some cases, Master closes connection of HTTP framework without deleting the heartbeater:
> https://github.com/apache/mesos/blob/65e18bef2c5ff356ef74bac9aa79b128c5b186d9/src/master/master.cpp#L3323
> https://github.com/apache/mesos/blob/65e18bef2c5ff356ef74bac9aa79b128c5b186d9/src/master/master.cpp#L10910
> It can be argued that this does not constitute a leak, because old heartbeaters are deleted on reconnection/removal.
> However, this means that for each disconnected framework there is a ResponseHeartbeaterProcess that performs an idle loop.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)