[
https://issues.apache.org/jira/browse/MESOS-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-887:
----------------------------------
Component/s: (was: slave)
framework
Description:
The Scheduler Driver already links with the master, but it does not use the
built in exited() notification from libprocess to detect socket closure.
Of particular concern is that, if the socket breaks and subsequent messages are
successfully sent on ephemeral sockets, then we don't re-register with the
master. Messages may have been dropped.
was:
The slave already links with the master, but it does not use the built in
exited() notification from libprocess to trigger re-registration.
Of particular concern is that, if the socket breaks and subsequent messages are
successfully sent on ephemeral sockets, then we don't re-register with the
master.
Summary: Scheduler driver should use exited() to detect disconnection
with Master. (was: Slave should use exited() to detect disconnection with
Master.)
> Scheduler driver should use exited() to detect disconnection with Master.
> -------------------------------------------------------------------------
>
> Key: MESOS-887
> URL: https://issues.apache.org/jira/browse/MESOS-887
> Project: Mesos
> Issue Type: Improvement
> Components: framework, master
> Affects Versions: 0.13.0, 0.14.0, 0.14.1, 0.14.2, 0.16.0, 0.15.0
> Reporter: Benjamin Mahler
> Labels: reliability
>
> The Scheduler Driver already links with the master, but it does not use the
> built in exited() notification from libprocess to detect socket closure.
> Of particular concern is that, if the socket breaks and subsequent messages
> are successfully sent on ephemeral sockets, then we don't re-register with
> the master. Messages may have been dropped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
