mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yan Xu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-7786) Create a convention for a special "no sender" PID.
Date Wed, 12 Jul 2017 20:14:00 GMT

     [ https://issues.apache.org/jira/browse/MESOS-7786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

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

> Create a convention for a special "no sender" PID.
> --------------------------------------------------
>
>                 Key: MESOS-7786
>                 URL: https://issues.apache.org/jira/browse/MESOS-7786
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>            Reporter: 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., {{@0.0.0.0:0}} 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|http://doc.akka.io/japi/akka/current/akka/actor/ActorRef.html#noSender--]
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 {{_@192.168.1.2:5050}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message