hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Koji Noguchi (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HDFS-304) Slow namenode webUI (Taking 1 minute to load on 2000 nodes cluster.)
Date Mon, 02 Nov 2009 20:32:59 GMT

     [ https://issues.apache.org/jira/browse/HDFS-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Koji Noguchi resolved HDFS-304.
-------------------------------

    Resolution: Duplicate

This was fixed as part of https://issues.apache.org/jira/browse/HADOOP-4029 "NameNode should
report status and performance for each replica of image and log"

As part of the Jira, it did "4. List of live/dead nodes is moved to a separate page. "  which
is good enough for me.


> Slow namenode webUI (Taking 1 minute to load on 2000 nodes cluster.)
> --------------------------------------------------------------------
>
>                 Key: HDFS-304
>                 URL: https://issues.apache.org/jira/browse/HDFS-304
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Koji Noguchi
>
> Showing the namenode webui takes a long time with large cluster 
> and also adds high cpu load to the namenode.  
> Is this expected? 
> WHILE pulling the namenode webUI, top showed 
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 20957 hadoop 16   0 20.3g  19g 4732 S  131 63.7   9767:05 java
> AFTER the pull
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 20957 hadoop  16   0 20.3g  19g 4732 S   24 63.7   9768:12 java
> It would be nice if we can improve this especially since we tend to hit the webUI when
namenode is having trouble.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message