[ 
https://issues.apache.org/jira/browse/MESOS-5740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356302#comment-15356302
 ] 

Joseph Wu edited comment on MESOS-5740 at 7/11/16 9:52 PM:
-----------------------------------------------------------

{code}
commit 482257a9f46ecab4f888af46cd514d29d7cfd980
Author: Joseph Wu <[email protected]>
Date:   Wed Jun 29 18:20:41 2016 -0700

    Added test-only function for retrieving link sockets from libprocess.
    
    This can be used in a test to "break" a socket without libprocess's
    explicit knowledge.  For example, we can disable transmission on a
    persistent link.  The next message sent over that link will be dropped.
    
    Review: https://reviews.apache.org/r/49174/
{code}
{code}
commit 3ae62e27ecb83da36849f6528b997d2087d330f2
Author: Joseph Wu <[email protected]>
Date:   Wed Jun 29 18:20:43 2016 -0700

    Added tests for libprocess linking and unlinking behavior.
    
    Adds tests which exercise "link" semantics against remote processes.
    This includes detection of `ExitedEvents` when the process exits
    as well as mixing "link" semantics.
    
    Includes a test case that emulates the failure observed in MESOS-5576.
    
    Review: https://reviews.apache.org/r/49175/
{code}
{code}
commit 414f937f270f1aadfe239d61a40ba88d5f2f0501
Date:   Wed Jun 29 18:20:44 2016 -0700

    Added "relink" semantics to ProcessBase::link.
    
    The `RemoteConnection:RECONNECT` option for `ProcessBase::link` will
    force the `SocketManager` to create a new socket if a persistent link
    already exists.
    
    Review: https://reviews.apache.org/r/49177/
{code}


was (Author: kaysoky):
{code}
commit 482257a9f46ecab4f888af46cd514d29d7cfd980
Author: Joseph Wu <[email protected]>
Date:   Wed Jun 29 18:20:41 2016 -0700

    Added test-only function for retrieving link sockets from libprocess.
    
    This can be used in a test to "break" a socket without libprocess's
    explicit knowledge.  For example, we can disable transmission on a
    persistent link.  The next message sent over that link will be dropped.
    
    Review: https://reviews.apache.org/r/49174/
{code}
{code}
commit 3ae62e27ecb83da36849f6528b997d2087d330f2
Author: Joseph Wu <[email protected]>
Date:   Wed Jun 29 18:20:43 2016 -0700

    Added tests for libprocess linking and unlinking behavior.
    
    Adds tests which exercise "link" semantics against remote processes.
    This includes detection of `ExitedEvents` when the process exits
    as well as mixing "link" semantics.
    
    Includes a test case that emulates the failure observed in MESOS-5576.
    
    Review: https://reviews.apache.org/r/49175/
{code}
{code}
commit 482257a9f46ecab4f888af46cd514d29d7cfd980
Date:   Wed Jun 29 18:20:44 2016 -0700

    Added "relink" semantics to ProcessBase::link.
    
    The `RemoteConnection:RECONNECT` option for `ProcessBase::link` will
    force the `SocketManager` to create a new socket if a persistent link
    already exists.
    
    Review: https://reviews.apache.org/r/49177/
{code}

> 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
>             Fix For: 0.28.3, 1.0.0
>
>
> 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)

Reply via email to