[
https://issues.apache.org/jira/browse/HDFS-14508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848609#comment-16848609
]
CR Hota commented on HDFS-14508:
--------------------------------
[~tasanuma] Thanks for starting the thread.
Its better to have a routerbeanmetrics that shares info about router itself
version, status, security etc and have one for federation, which is for the
whole federation as the name suggests.
The reason I am looking at a new bean dedicated for router is that Namenode
bean has methods specific to namenodes (getSlowPeersReport, getSlowDisksReport
etc etc ) that isn't applicable to routers and also in the future if any change
is done (for ex adding a new metric specific to namenode) then router also has
to dummy implement it. It's better to de-couple. Though they look same to API
users, routers and namenodes are fundamentally quite different.
> RBF: Clean-up and refactor UI components
> ----------------------------------------
>
> Key: HDFS-14508
> URL: https://issues.apache.org/jira/browse/HDFS-14508
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: CR Hota
> Assignee: Takanobu Asanuma
> Priority: Minor
>
> Router UI has tags that are not used or incorrectly set. The code should be
> cleaned-up.
> One such example is
> Path :
> (\hadoop-hdfs-project\hadoop-hdfs-rbf\src\main\webapps\router\federationhealth.js)
> {code:java}
> {"name": "routerstat", "url":
> "/jmx?qry=Hadoop:service=NameNode,name=NameNodeStatus"},{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
