You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Greg Mann (JIRA)" <ji...@apache.org> on 2017/05/23 23:48:04 UTC
[jira] [Created] (MESOS-7551) Associate libprocess delays uniquely
with a ProcessReference
Greg Mann created MESOS-7551:
--------------------------------
Summary: Associate libprocess delays uniquely with a ProcessReference
Key: MESOS-7551
URL: https://issues.apache.org/jira/browse/MESOS-7551
Project: Mesos
Issue Type: Improvement
Components: libprocess
Reporter: Greg Mann
Currently, when a libprocess actor calls {{delay}}, the target PID is passed to {{ProcessManager::deliver}}, which looks up the target with {{use()}}. This means that the process is looked up using its process ID, rather than using a unique process reference.
This means that when running a test in repetition, it's possible that delays executed by a particular actor can be unexpectedly dispatched to an actor with the same process ID in subsequent iterations of the test. This can be an issue when actors are initialized explicitly with a particular PID.
We could instead capture a {{ProcessReference}} when the delay is initially called, and dispatch to the unique reference.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)