Return-Path: X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-common-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 D4DBA18B97 for ; Wed, 24 Jun 2015 19:56:06 +0000 (UTC) Received: (qmail 24749 invoked by uid 500); 24 Jun 2015 19:56:06 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 24702 invoked by uid 500); 24 Jun 2015 19:56:06 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 24682 invoked by uid 99); 24 Jun 2015 19:56:06 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2015 19:56:06 +0000 Date: Wed, 24 Jun 2015 19:56:06 +0000 (UTC) From: "Jonathan Eagles (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HADOOP-11958) MetricsSystemImpl fails to show backtrace when an error occurs 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/HADOOP-11958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Eagles updated HADOOP-11958: ------------------------------------- Fix Version/s: 2.8.0 3.0.0 > MetricsSystemImpl fails to show backtrace when an error occurs > -------------------------------------------------------------- > > Key: HADOOP-11958 > URL: https://issues.apache.org/jira/browse/HADOOP-11958 > Project: Hadoop Common > Issue Type: Bug > Reporter: Jason Lowe > Assignee: Jason Lowe > Fix For: 3.0.0, 2.8.0 > > Attachments: HADOOP-11958.001.patch > > > While investigating YARN-3619 it was frustrating that MetricsSystemImpl was logging a ConcurrentModificationException but without any backtrace. Logging a backtrace would be very beneficial to tracking down the cause of the problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)