hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-1873) Federation Cluster Management Web Console
Date Sun, 01 May 2011 20:32:05 GMT

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

Philip Zeyliger commented on HDFS-1873:
---------------------------------------

Hi,

Absolutely excellent to have a web UI here; thanks for making it!

A few comments on the JMX approach:

(1) The namenode already has a port open for the Namenode RPC protocol and another one open
for HTTP.  Have you considered adding a getWhatever() API to the namenode RPC protocol or
adding a Jetty servlet endpoint for the same?  Either approach would require less configuration.
 We already have two perfectly good protocols; why bother with a third?  (

(2) You provide a way to set the agent port, but, ultimately, there are a lot of properties
involved in setting up JMX (http://download.oracle.com/javase/6/docs/technotes/guides/management/agent.html
has ones for security, SSL, passwords and credentials, etc.)  As you know, once you connect
via JMX, you can do pretty much anything, including injecting code into the namenode. It seems
that setting '-Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false'
(as you do in one of the patches in the subissues) by default is unwise from a security perspective.


(3) The method you use to get the config from hdfs-site to the shell script ends up creating
an extra JVM.  That's not terrible: it's not that Hadoop startup time is particularly speedy
to begin with, but we already have options in hadoop-env.sh (like heapsize), so the extra
mechanism feels like it may be gratuitous.  I looked around to see if there was a way to start
(or open) the JMX agent port programatically, but I did not find one.

Cheers,

-- Philip

> Federation Cluster Management Web Console
> -----------------------------------------
>
>                 Key: HDFS-1873
>                 URL: https://issues.apache.org/jira/browse/HDFS-1873
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>    Affects Versions: 0.23.0
>            Reporter: Tanping Wang
>            Assignee: Tanping Wang
>             Fix For: 0.23.0
>
>         Attachments: ClusterSummary.png, Decommission.png, HDFS-1873.patch
>
>
> The Federation cluster management console provides 
> # Cluster summary information that shows overall cluster utilization.  A list of the
name nodes that reports the used space, files and directories, blocks, live and dead datanodes

> of each name space.
> # decommissioning status of all the data nodes who are decommissioning in process or
decommissioned.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message