[ https://issues.apache.org/jira/browse/HDFS-14508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16848597#comment-16848597 ]
Takanobu Asanuma commented on HDFS-14508: ----------------------------------------- This is [~crh]'s comment in HDFS-14475: {quote} Fundamentally since router is becoming more intelligent, it may be a good idea to expose metrics separately and not necessarily implement NamenodeBeanMetrics which has methods specific to namenode and not applicable to Routers. {quote} In addition to that, {{FederationMetrics}} covers most of the metrics of {{NamenodeBeanMetrics}} at the moment. Given that, can we put them together into {{FederationMetrics}} and remove {{NamenodeBeanMetrics}}? Or is there any reason that we should keep {{NamenoeBeanMetrics}}? > 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