Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E792318BF3 for ; Tue, 30 Jun 2015 04:17:11 +0000 (UTC) Received: (qmail 53233 invoked by uid 500); 30 Jun 2015 04:17:11 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 53192 invoked by uid 500); 30 Jun 2015 04:17:11 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 53176 invoked by uid 99); 30 Jun 2015 04:17:11 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2015 04:17:11 +0000 Date: Tue, 30 Jun 2015 04:17:11 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-1848) Persist ClusterMetrics across RM HA transitions 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/YARN-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kumar Vavilapalli updated YARN-1848: ------------------------------------------ Target Version/s: 2.6.1, 2.7.2 (was: 2.6.0) Moving all tickets targeted for the already closed release 2.6.0 into 2.6.1/2.7.2. > Persist ClusterMetrics across RM HA transitions > ----------------------------------------------- > > Key: YARN-1848 > URL: https://issues.apache.org/jira/browse/YARN-1848 > Project: Hadoop YARN > Issue Type: Sub-task > Components: resourcemanager > Affects Versions: 2.4.0 > Reporter: Karthik Kambatla > > Post YARN-1705, ClusterMetrics are reset on transition to standby. This is acceptable as the metrics show statistics since an RM has become active. Users might want to see metrics since the cluster was ever started. -- This message was sent by Atlassian JIRA (v6.3.4#6332)