hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jing Zhao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5693) Few NN metrics data points were collected via JMX when NN is under heavy load
Date Tue, 22 Apr 2014 23:50:20 GMT

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

Jing Zhao commented on HDFS-5693:
---------------------------------

The new patch actually still includes the quick check in listCorruptFileBlocks :) But we can
make further changes in HDFS-6272. +1 pending Jenkins.

> Few NN metrics data points were collected via JMX when NN is under heavy load
> -----------------------------------------------------------------------------
>
>                 Key: HDFS-5693
>                 URL: https://issues.apache.org/jira/browse/HDFS-5693
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: HADOOP-5693.patch, HDFS-5693-2.patch, HDFS-5693.patch
>
>
> JMX sometimes doesn’t return any value when NN is under heavy load. However, that is
when we would like to get metrics to help to diagnosis the issue.
> When NN is under heavy load due to bad application or other reasons, it holds FSNamesystem's
writer lock for a long period of time. Many of the FSNamesystem metrics require FSNamesystem's
reader lock and thus can't be processed.
> This is a special case to improve the overall NN concurrency.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message