You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Anand Mazumdar (JIRA)" <ji...@apache.org> on 2016/05/11 16:42:13 UTC
[jira] [Created] (MESOS-5364) Consider adding `unlink`
functionality to libprocess
Anand Mazumdar created MESOS-5364:
-------------------------------------
Summary: 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
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)