[
https://issues.apache.org/jira/browse/MESOS-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15354394#comment-15354394
]
Joseph Wu edited comment on MESOS-5740 at 6/29/16 2:27 AM:
-----------------------------------------------------------
|| Review || Summary ||
| https://reviews.apache.org/r/49174/ | Test-only libprocess hook |
| https://reviews.apache.org/r/49175/ | Tests + repro |
| https://reviews.apache.org/r/49177/ | Implement "relink" |
was (Author: kaysoky):
|| Review || Summary ||
| https://reviews.apache.org/r/49174/ | Test-only libprocess hook |
| https://reviews.apache.org/r/49175/ | Tests + repro |
| https://reviews.apache.org/r/49177/ | Implement "relink" |
| https://reviews.apache.org/r/49346/ | Network.hpp + relink |
> Consider adding `relink` functionality to libprocess
> ----------------------------------------------------
>
> Key: MESOS-5740
> URL: https://issues.apache.org/jira/browse/MESOS-5740
> Project: Mesos
> Issue Type: Improvement
> Components: libprocess
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: libprocess, mesosphere
>
> Currently we don't have the {{relink}} functionality in libprocess. i.e. A
> way to create a new persistent connection between actors, even if a
> connection already exists.
> This can benefit us in a couple of ways:
> - The application may have more information on the state of a connection than
> libprocess does, as libprocess only checks if the connection is alive or not.
> For example, a linkee may accept a connection, then fork, pass the
> connection to a child, and subsequently exit. As the connection is still
> active, libprocess may not detect the exit.
> - 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
