Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Fri, 10 May 2013 18:11:17 +0000 (UTC)
From: "Mostafa Elhemali (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12647065.1368209436637.301423.1368209477058@arcas>
In-Reply-To: <JIRA.12647065.1368209436637@arcas>
References: <JIRA.12647065.1368209436637@arcas>
Subject: [jira] [Created] (HADOOP-9559) When metrics system is restarted
 MBean names get incorrectly flagged as dupes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Mostafa Elhemali created HADOOP-9559:
----------------------------------------

             Summary: When metrics system is restarted MBean names get incorrectly flagged as dupes
                 Key: HADOOP-9559
                 URL: https://issues.apache.org/jira/browse/HADOOP-9559
             Project: Hadoop Common
          Issue Type: Bug
            Reporter: Mostafa Elhemali
            Assignee: Mostafa Elhemali


In the Metrics2 system, every source gets registered as an MBean name, which gets put into a unique name pool in the singleton DefaultMetricsSystem object. The problem is that when the metrics system is shutdown (which unregisters the MBeans) this unique name pool is left as is, so if the metrics system is started again every attempt to register the same MBean names fails (exception is eaten and a warning is logged).
I think the fix here is to remove the name from the unique name pool if an MBean is unregistered, since it's OK at this point to add it again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira