Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sun, 13 Mar 2016 15:39:33 +0000 (UTC)
From: "Daniel Templeton (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12949372.1457738045000.2476.1457883573445@Atlassian.JIRA>
In-Reply-To: <JIRA.12949372.1457738045000@Atlassian.JIRA>
References: <JIRA.12949372.1457738045000@Atlassian.JIRA>
 <JIRA.12949372.1457738045241@arcas>
Subject: [jira] [Resolved] (YARN-4799) ContainerMetrics drops records
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Daniel Templeton resolved YARN-4799.
------------------------------------
    Resolution: Duplicate

> ContainerMetrics drops records
> ------------------------------
>
>                 Key: YARN-4799
>                 URL: https://issues.apache.org/jira/browse/YARN-4799
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.9.0
>            Reporter: Daniel Templeton
>            Assignee: Daniel Templeton
>
> The metrics2 system was implemented to deal with persistent sources.  {{ContainerMetrics}} is an ephemeral source, and so it causes problems.  Specifically, the {{ContainerMetrics}} only reports metrics once after the container has been stopped.  This behavior is a problem because the metrics2 system can ask sources for reports that will be quietly dropped by the sinks that care.  (It's a metrics2 feature, not a bug.)  If that final report is silently dropped, it's lost, because the {{ContainerMetrics}} won't report anything else ever anymore.


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