Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9C05510041 for ; Mon, 2 Feb 2015 22:54:56 +0000 (UTC) Received: (qmail 70294 invoked by uid 500); 2 Feb 2015 22:54:57 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 70264 invoked by uid 500); 2 Feb 2015 22:54:57 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 70252 invoked by uid 99); 2 Feb 2015 22:54:57 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Feb 2015 22:54:57 +0000 Date: Mon, 2 Feb 2015 22:54:57 +0000 (UTC) From: "Hudson (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-9418) UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for slaves such as DataNodes and NodeManagers MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-9418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302169#comment-14302169 ] Hudson commented on AMBARI-9418: -------------------------------- FAILURE: Integrated in Ambari-trunk-Commit-docker #841 (See [https://builds.apache.org/job/Ambari-trunk-Commit-docker/841/]) AMBARI-9418 UI changes to resolve discrepancies between what the stack vs Ambari reports as "live" for slaves such as DataNodes and NodeManagers. (ababiichuk) (ababiichuk: http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=f1bc1bdad427e8d81d3f3776e80f8b8ed73cf218) * ambari-web/test/models/service/yarn_test.js * ambari-web/app/controllers/global/update_controller.js * ambari-web/app/views/main/service/services/hdfs.js * ambari-web/app/models/service/yarn.js * ambari-web/app/views/main/dashboard/widgets/node_managers_live.js * ambari-web/app/views/main/dashboard/widgets/datanode_live.js * ambari-web/app/templates/main/service/services/hdfs.hbs * ambari-web/app/mappers/service_metrics_mapper.js * ambari-web/app/models/service/hdfs.js * ambari-web/app/templates/main/service/services/yarn.hbs * ambari-web/app/messages.js * ambari-web/test/controllers/global/update_controller_test.js > 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)