You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Jing Zhao (JIRA)" <ji...@apache.org> on 2015/01/09 22:38:34 UTC

[jira] [Commented] (HDFS-7182) JMX metrics aren't accessible when NN is busy

    [ https://issues.apache.org/jira/browse/HDFS-7182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14271908#comment-14271908 ] 

Jing Zhao commented on HDFS-7182:
---------------------------------

Currently we check if rollingUpgradeInfo is null to determine if rolling upgrade is in process. Without the read lock do we need to declare the object as volatile to make sure the jmx returns the correct result?

> JMX metrics aren't accessible when NN is busy
> ---------------------------------------------
>
>                 Key: HDFS-7182
>                 URL: https://issues.apache.org/jira/browse/HDFS-7182
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: HDFS-7182-2.patch, HDFS-7182.patch
>
>
> HDFS-5693 has addressed all NN JMX metrics in hadoop 2.0.5. Since then couple new metrics have been added. It turns out "RollingUpgradeStatus" requires FSNamesystem read lock.



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