[
https://issues.apache.org/jira/browse/AMBARI-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298888#comment-14298888
]
Hadoop QA commented on AMBARI-9418:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12695555/AMBARI-9418.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1539//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1539//console
This message is automatically generated.
> 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)
