[
https://issues.apache.org/jira/browse/MESOS-2484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359108#comment-14359108
]
Dominic Hamon commented on MESOS-2484:
--------------------------------------
see also https://issues.apache.org/jira/browse/MESOS-1456 regarding metrics.
there's been some discussion about enforcing unique PID ids for every process
but I can't find the relevant JIRA ticket.
> libprocess Clock messages delivered
> ------------------------------------
>
> Key: MESOS-2484
> URL: https://issues.apache.org/jira/browse/MESOS-2484
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: Cody Maloney
>
> Found in / discussed at: https://reviews.apache.org/r/30587/#rc118737-72676
> When a process is terminated, any outstanding delay() destined for that
> process aren't terminated, meaning they arrive whenever the clock happens to
> get there. With uniquely named processes this isn't an issue, but with names
> that are reused (master), it could potentially lead to odd test flakiness,
> and is artifacts carrying across / between tests which shouldn't be.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
