[
https://issues.apache.org/jira/browse/MESOS-5364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15353931#comment-15353931
]
Joseph Wu commented on MESOS-5364:
----------------------------------
Note: Due to a similar issue with stale links, we will be introducing "relink"
semantics to libprocess. Relinking provides better guarantees than "unlinking"
because the application is guaranteed to have a new socket connection,
regardless of other linkers.
Here's an example of how relink is used: https://reviews.apache.org/r/49346/
> Consider adding `unlink` functionality to libprocess
> ----------------------------------------------------
>
> Key: MESOS-5364
> URL: https://issues.apache.org/jira/browse/MESOS-5364
> Project: Mesos
> Issue Type: Improvement
> Reporter: Anand Mazumdar
> Labels: libprocess, mesosphere
>
> Currently we don't have the {{unlink}} functionality in libprocess i.e.
> Erlang's equivalent of http://erlang.org/doc/man/erlang.html#unlink-1. We
> have a lot of places in our current code with {{TODO's}} for implementing it.
> It can benefit us in a couple of ways:
> - Based on the business logic of the actor, it would want to authoritatively
> communicate that it is no longer interested in {{ExitedEvent}} for the
> external remote link.
> - Sometimes, the {{ExitedEvent}} might be delayed or might be dropped due to
> the remote instance being unavailable (e.g., partition, network
> intermediaries not sending RST's etc).
> I did not find any old JIRA's pertaining to this but I did come across an
> initial attempt to add this though albeit for injecting {{exited}} events as
> part of the initial review for MESOS-1059.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
