mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dominic Hamon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-1456) Metric lifetime should be tied to process runstate, not lifetime.
Date Tue, 11 Nov 2014 22:58:34 GMT

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

Dominic Hamon updated MESOS-1456:
---------------------------------
    Sprint: Mesos Q3 Sprint 6, Twitter Q4 Sprint 1, Twitter Mesos Q4 Sprint 2  (was: Mesos
Q3 Sprint 6, Twitter Q4 Sprint 1, Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3)

> Metric lifetime should be tied to process runstate, not lifetime.
> -----------------------------------------------------------------
>
>                 Key: MESOS-1456
>                 URL: https://issues.apache.org/jira/browse/MESOS-1456
>             Project: Mesos
>          Issue Type: Bug
>          Components: statistics
>    Affects Versions: 0.19.0
>            Reporter: Dominic Hamon
>            Assignee: Dominic Hamon
>
> The usual pattern for termination of processes is {{terminate(..); wait(..); delete ..;}}
but the {{SchedulerProcess}} is terminated and then deleted some time later.
> If the metrics endpoint is accessed within that period, it never returns as it tries
to access a {{Gauge}} that has a reference to a valid PID that is not getting any timeslices
(the {{SchedulerProcess}}). A one-off fix can be made to the {{SchedulerProcess}} to move
the metrics add/remove calls to {{initialize}} and {{finalize}}, but this should be the general
pattern for every process with metrics. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message