FAQ
[ 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.

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouphdfs-dev @
categorieshadoop
postedNov 2, '09 at 8:33p
activeNov 2, '09 at 8:33p
posts1
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Koji Noguchi (JIRA): 1 post

People

Translate

site design / logo © 2022 Grokbase