You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2019/02/20 18:37:00 UTC

[jira] [Commented] (MESOS-7568) Introduce a heartbeat mechanism for v0 executor <-> agent links.

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

Greg Mann commented on MESOS-7568:
----------------------------------

[~kaysoky] is this still an issue for v0 executors?

> Introduce a heartbeat mechanism for v0 executor <-> agent links.
> ----------------------------------------------------------------
>
>                 Key: MESOS-7568
>                 URL: https://issues.apache.org/jira/browse/MESOS-7568
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: Anand Mazumdar
>            Priority: Critical
>              Labels: foundations, mesosphere
>
> Currently, we do not have heartbeats for executor <-> agent communication. This is especially problematic in scenarios when IPFilters are enabled since the default conntrack keep alive timeout is 5 days. When that timeout elapses, the executor doesn't get notified via a socket disconnection when the agent process restarts. The executor would then get killed if it doesn't re-register when the agent recovery process is completed.
> Enabling application level heartbeats or TCP KeepAlive's can be a possible way for fixing this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)