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

Ilya Pronin updated MESOS-8493:
-------------------------------
    Description: 
Currently if the task status update has no reason we don't increment 
{{master/<state>/<source>/<reason>}} metric. Because of that 
{{master/task_<state>/*}} counters may not sum up to {{master/tasks_<state>}} 
counter, if for example a custom executor doesn't set the reason in its status 
updates.

Since the zero value in {{Reason}} enum is already taken it is possible to just 
count status updates with no reason an under artificial {{reason_unknown}} name.

  was:
Currently if the task status update has no reason we don't increment 
{{master/<state>/<source>/<reason>}} metric. Because of that 
{{master/task_<status>/*}} counters may not sum up to {{master/tasks_<status>}} 
counter, if for example a custom executor doesn't set a reason to its status 
updates.

Since the zero value in {{Reason}} enum is already taken it is possible to just 
count status updates with no reason an under artificial {{reason_unknown}} name.


> Master task state metrics discrepancy
> -------------------------------------
>
>                 Key: MESOS-8493
>                 URL: https://issues.apache.org/jira/browse/MESOS-8493
>             Project: Mesos
>          Issue Type: Improvement
>          Components: master
>    Affects Versions: 1.2.0
>            Reporter: Ilya Pronin
>            Priority: Trivial
>
> Currently if the task status update has no reason we don't increment 
> {{master/<state>/<source>/<reason>}} metric. Because of that 
> {{master/task_<state>/*}} counters may not sum up to {{master/tasks_<state>}} 
> counter, if for example a custom executor doesn't set the reason in its 
> status updates.
> Since the zero value in {{Reason}} enum is already taken it is possible to 
> just count status updates with no reason an under artificial 
> {{reason_unknown}} name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to