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

Gavin updated MESOS-7551:
-------------------------
    Comment: was deleted

(was: www.rtat.net)

> Libprocess delays / defers may run on a Process with re-used PID.
> -----------------------------------------------------------------
>
>                 Key: MESOS-7551
>                 URL: https://issues.apache.org/jira/browse/MESOS-7551
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>            Reporter: Greg Mann
>            Priority: Major
>              Labels: integration, mesosphere
>
> 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
(v7.6.3#76005)

Reply via email to