[
https://issues.apache.org/jira/browse/MESOS-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664504#comment-16664504
]
Greg Mann commented on MESOS-7564:
----------------------------------
I think that luckily the backward-compatibility story of this change should be
fairly simple; executors can opt-in to heartbeats in their SUBSCRIBE call,
either with a special field or by specifying the correct Content-Type.
We've had some users with CNI deployments that close executor <=> agent
connections after extended periods of inactivity, so this fix will be
prioritized soon.
> Introduce a heartbeat mechanism for v1 HTTP executor <-> agent communication.
> -----------------------------------------------------------------------------
>
> Key: MESOS-7564
> URL: https://issues.apache.org/jira/browse/MESOS-7564
> Project: Mesos
> Issue Type: Bug
> Reporter: Anand Mazumdar
> Priority: Critical
> Labels: 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)
