[jira] [Updated] (AMBARI-9418) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for slaves such as DataNodes and NodeManagers

["Andrii Babiichuk (JIRA)" <ji...@apache.org>]

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

Andrii Babiichuk updated AMBARI-9418:
-------------------------------------
    Attachment: AMBARI-9418.patch

> UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for slaves such as DataNodes and NodeManagers
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9418
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9418
>             Project: Ambari
>          Issue Type: Task
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Andrii Babiichuk
>            Assignee: Andrii Babiichuk
>            Priority: Critical
>             Fix For: 2.0.0
>
>         Attachments: AMBARI-9418.patch
>
>
> Sometimes there are discrepancies between what the stack reports as being live vs Ambari reports as live.
> This comes from the fact that liveness is tracked by the service master differently than simply process up/down, which Ambari reports.
> Strictly speaking, Ambari reports both, but how UI is presenting it now creates confusion.



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