[jira] [Updated] (AURORA-1910) framework_registered metric isn't reset when scheduler disconnects

2017-06-09 Thread Santhosh Kumar Shanmugham (JIRA)

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

Santhosh Kumar Shanmugham updated AURORA-1910:
--
Fix Version/s: 0.18.0

> framework_registered metric isn't reset when scheduler disconnects
> --
>
> Key: AURORA-1910
> URL: https://issues.apache.org/jira/browse/AURORA-1910
> Project: Aurora
>  Issue Type: Bug
>Reporter: Zameer Manji
>Assignee: Zameer Manji
> Fix For: 0.18.0
>
>
> Right now the {{framework_registered}} metric transitions from 0 -> 1 when 
> the scheduler registers successfully the first time. It never transitions 
> from 1 -> 0 when it loses a connection.
> This metric is already a gauge of an {{AtomicBoolean}}. We should adjust the 
> gauge as the scheduler loses registration and re-registers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (AURORA-1910) framework_registered metric isn't reset when scheduler disconnects

2017-03-28 Thread Zameer Manji (JIRA)

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

Zameer Manji updated AURORA-1910:
-
Summary: framework_registered metric isn't reset when scheduler disconnects 
 (was: framework_registered metric doesn't reset when scheduler disconnects)

> framework_registered metric isn't reset when scheduler disconnects
> --
>
> Key: AURORA-1910
> URL: https://issues.apache.org/jira/browse/AURORA-1910
> Project: Aurora
>  Issue Type: Bug
>Reporter: Zameer Manji
>Assignee: Zameer Manji
>
> Right now the {{framework_registered}} metric transitions from 0 -> 1 when 
> the scheduler registers successfully the first time. It never transitions 
> from 1 -> 0 when it loses a connection.
> This metric is already a gauge of an {{AtomicBoolean}}. We should adjust the 
> gauge as the scheduler loses registration and re-registers.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)