[
https://issues.apache.org/jira/browse/MESOS-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Mahler updated MESOS-1963:
-----------------------------------
Description:
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 and re-link
with the master. Inconsistency can arise as a result of this, since we
currently rely on re-registration to reconcile state when messages are 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. Inconsistency can arise as a result of this, since we currently rely on
re-registration to reconcile state when messages are dropped.
> Slave should use exited() to detect disconnection with Master.
> --------------------------------------------------------------
>
> Key: MESOS-1963
> URL: https://issues.apache.org/jira/browse/MESOS-1963
> Project: Mesos
> Issue Type: Improvement
> Components: master, slave
> Reporter: Benjamin Mahler
> Labels: reliability, twitter
>
> 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 and
> re-link with the master. Inconsistency can arise as a result of this, since
> we currently rely on re-registration to reconcile state when messages are
> dropped.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
