mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <>
Subject [jira] [Updated] (MESOS-7786) Create a special "no sender" PID.
Date Thu, 13 Jul 2017 23:01:00 GMT


Yan Xu updated MESOS-7786:
    Summary: Create a special "no sender" PID.  (was: Create a convention for a special "no
sender" PID.)

> Create a special "no sender" PID.
> ---------------------------------
>                 Key: MESOS-7786
>                 URL:
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess
>            Reporter: Yan Xu
>            Assignee: Yan Xu
> In libprocess we have this "fire and forget" messaging semantics, (e.g., MESOS-7753 and
a few places in tests).
> Right now these kind of messages use an empty sender PID, i.e., {{@}} which
is could fail some checks like MESOS-7401.
> At a high level I think 
> - It's OK if libprocess messages don't have a sender actor, akin to the [no-sender|]
concept in Akka.
> - However all remote messages should have a valid source address i.e., ip and port in
its {{Libprocess-From}}.
> So we can create a special *no-sender* ID and just make sure real actors can't use this
ID. The ID could {{\_\_no\_sender\_\_}} or simply {{\_}}? The UPID would then look like {{_@}}.

This message was sent by Atlassian JIRA

View raw message