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 "Chen Liang (JIRA)" <ji...@apache.org> on 2017/04/03 18:24:42 UTC
[jira] [Assigned] (HDFS-11586) Report %free, %write_locked,
%read_locked for the NameNode FSNamesystemLock
[ https://issues.apache.org/jira/browse/HDFS-11586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chen Liang reassigned HDFS-11586:
---------------------------------
Assignee: Chen Liang
> Report %free, %write_locked, %read_locked for the NameNode FSNamesystemLock
> ---------------------------------------------------------------------------
>
> Key: HDFS-11586
> URL: https://issues.apache.org/jira/browse/HDFS-11586
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Zheng Shao
> Assignee: Chen Liang
> Priority: Minor
>
> It's useful to understand how busy the NameNode is by providing these metrics, similar to the %util number from iostat for disks.
> When %free goes to close to 0, we know the NameNode is congested (just like when disk %util goes to 100%).
> This can be implemented very cheaply by using a thread that wakes up every 10ms to check FSNamesystemLock's getReadLockCount() and isWriteLocked() (via the member coarseLock).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org