[
https://issues.apache.org/jira/browse/HDFS-14475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16847724#comment-16847724
]
CR Hota commented on HDFS-14475:
--------------------------------
[~tasanuma] Thanks for looking into this.
I would just leave this as is and see how we can consolidate in the refactoring
jira. As I had mentioned earlier, there is few things which should be re-looked
at wrt metrics. For now federation can continue to expose status, token counts,
security etc. Can you help start the conversation in HDFS-14508. 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.
> RBF: Expose router security enabled status on the UI
> ----------------------------------------------------
>
> Key: HDFS-14475
> URL: https://issues.apache.org/jira/browse/HDFS-14475
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: CR Hota
> Assignee: CR Hota
> Priority: Major
> Attachments: HDFS-14475-HDFS-13891.001.patch,
> HDFS-14475-HDFS-13891.002.patch
>
>
> This is a branched off Jira to expose metric so that router's security status
> can be displayed on the UI. We are still unclear if more work needs to be
> done for dealing with CORS etc.
> https://issues.apache.org/jira/browse/HDFS-12510 will continue to track that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]