[MESOS-5364] Consider adding `unlink` functionality to libprocess

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: libprocess mesosphere
• Assignee: Unassigned
• Reporter: Anand Mazumdar
• Created: 11/May/16 16:41
• Updated: 03/Feb/17 18:45
• Resolved: 03/Feb/17 18:45

Description

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.

Issue Links

• is related to: MESOS-5332 TASK_LOST on slave restart potentially due to executor race condition
• relates to: MESOS-5576 Masters may drop the first message they send between masters after a network partition
• relates to: MESOS-5740 Consider adding `relink` functionality to libprocess