You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Neil Conway (JIRA)" <ji...@apache.org> on 2017/05/31 18:07:04 UTC
[jira] [Commented] (MESOS-7596) Multiple registration attempts
might result in agent shutdown.
[ https://issues.apache.org/jira/browse/MESOS-7596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031607#comment-16031607 ]
Neil Conway commented on MESOS-7596:
------------------------------------
Related: https://reviews.apache.org/r/59685
> Multiple registration attempts might result in agent shutdown.
> --------------------------------------------------------------
>
> Key: MESOS-7596
> URL: https://issues.apache.org/jira/browse/MESOS-7596
> Project: Mesos
> Issue Type: Bug
> Reporter: Neil Conway
> Labels: mesosphere
>
> This sequence of events is possible:
> # Agent sends register message M1 to master.
> # Agent register timer expires, sends register message M2 to master.
> # Master sees M1 and adds agent with ID A1.
> # Agent gets SlaveRegisteredMessage with ID A1.
> # The master <-> agent socket breaks; the master marks the agent as disconnected.
> # Master sees M2; since the agent is currently disconnected, the master removes A1 and adds the agent with ID A2.
> # Agent gets SlaveRegisteredMessage with ID A2. Since this is unexpected, the agent exits ("Registered but got wrong id").
> Shutting down the agent is unfortunate, although arguably not catastrophic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)