[
https://issues.apache.org/jira/browse/MESOS-5468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anand Mazumdar updated MESOS-5468:
----------------------------------
Summary: Add logic in long-lived-framework to handle network partitions.
(was: Add logic to long-lived-framework to handle HEARTBEAT timeout)
> Add logic in long-lived-framework to handle network partitions.
> ---------------------------------------------------------------
>
> Key: MESOS-5468
> URL: https://issues.apache.org/jira/browse/MESOS-5468
> Project: Mesos
> Issue Type: Bug
> Components: framework, master
> Reporter: Jay Guo
>
> Currently long-lived-framework does not handle HEARTBEAT timeout. If master
> teardown the framework without framework being aware of it (network
> partition), the framework keeps waiting for {{Event}} until reconnected.
> *On the other hand*, should we close TCP socket on master side when teardown
> a framework? Currently the tcp socket is left alive even framework has been
> deactivated. This results in framework sending invalid {{Call}} to master and
> re-detection.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
