hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7239) Create a servlet for HDFS UI
Date Mon, 13 Oct 2014 21:37:34 GMT

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

Suresh Srinivas commented on HDFS-7239:

[~wheat9], JMX interface was introduced to dissuade users from scraping namenode web UI. Since
then, anytime a namenode web UI change is introduced, we have also added equivalent JMX interface
method/functionality. Moving web UI to use JMX is great to ensure all UI related APIs are
available and is maintained and independent UI can be built. If we move all such future functionality
to a new servlet, where does that leave JMX interface?

> Create a servlet for HDFS UI
> ----------------------------
>                 Key: HDFS-7239
>                 URL: https://issues.apache.org/jira/browse/HDFS-7239
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>            Assignee: Haohui Mai
> Currently the HDFS UI gathers most of its information from JMX. There are a couple disadvantages:
> * JMX is also used by management tools, thus Hadoop needs to maintain compatibility across
minor releases.
> * JMX organizes information as <key, value> pairs. The organization does not fit
well with emerging use cases like startup progress report and nntop.
> This jira proposes to introduce a new servlet in the NN for the purpose of serving information
to the UI.
> It should be viewed as a part of the UI. There is *no* compatibility guarantees for the
output of the servlet.

This message was sent by Atlassian JIRA

View raw message