[ https://issues.apache.org/jira/browse/MESOS-6246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joseph Wu updated MESOS-6246: ----------------------------- Fix Version/s: 1.0.2 1.1.0 0.28.3 {code} commit 073bc6aa9cb21e6655e0089481fdf51ecbef722b Author: Joseph Wu <jos...@mesosphere.io> Date: Wed Sep 28 12:33:43 2016 -0700 Added ExitedEvents for links whose sockets fail on creation. When we try to link to a remote process, we will send the linkee an `ExitedEvent` when the link is broken or if the connection fails. This patch adds an `ExitedEvent` when the socket creation step fails. This is logically equivalent to having the connection step fail. Because this is an entirely unexpected case, the log level should be a WARNING or higher. Review: https://reviews.apache.org/r/52180/ {code} > Libprocess links will not generate an ExitedEvent if the socket creation fails > ------------------------------------------------------------------------------ > > Key: MESOS-6246 > URL: https://issues.apache.org/jira/browse/MESOS-6246 > Project: Mesos > Issue Type: Bug > Components: libprocess > Affects Versions: 0.27.3, 0.28.2, 1.0.1 > Reporter: Joseph Wu > Assignee: Joseph Wu > Labels: libprocess, mesosphere > Fix For: 0.28.3, 1.1.0, 1.0.2 > > > Noticed this while inspecting nearby code for potential races. > Normally, when a libprocess actor (the "linkee") links to a remote process, > it does the following: > 1) Create a socket. > 2) Connect to the remote process (asynchronous). > 3) Check the connection succeeded. > If (2) or (3) fail, the linkee will receive a {{ExitedEvent}}, which > indicates that the link broke. In case (1) fails, there is no > {{ExitedEvent}}: > https://github.com/apache/mesos/blob/7c833abbec9c9e4eb51d67f7a8e7a8d0870825f8/3rdparty/libprocess/src/process.cpp#L1558-L1562 -- This message was sent by Atlassian JIRA (v6.3.4#6332)