[
https://issues.apache.org/jira/browse/HDFS-14593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16876772#comment-16876772
]
Takanobu Asanuma commented on HDFS-14593:
-----------------------------------------
I looked into the namenodes case. Actually, it is a bit different from the
router case.
*NameNode*:
When a namenode is set to {{dfs.federation.router.monitor.namenode}}, the
configured router registers the namenode to State Store. Then, if the namenode
is removed from {{dfs.federation.router.monitor.namenode}}, the namenode
becomes EXPIRED. Router Web UI(Nameservice Information) doesn't show EXPIRED
namenodes but the EXPIRED namenodes are stored in State Store forever. They are
not removed from State Store.
*Router*:
When a router starts at first time, it registers itself to State Store. Then,
if the router is unavailable, it becomes EXPIRED. Router Web UI(Routers
Information) shows all routers in State Store even if the status of the router
is EXPIRED. So EXPIRED routers show on the Web UI and are stored in State Store
forever.
What should we do?
> RBF: RouterAdmin should be able to remove expired routers from Routers
> Information
> ----------------------------------------------------------------------------------
>
> Key: HDFS-14593
> URL: https://issues.apache.org/jira/browse/HDFS-14593
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: rbf
> Reporter: Takanobu Asanuma
> Assignee: Takanobu Asanuma
> Priority: Major
> Attachments: HDFS-14593.001.patch, HDFS-14593.002.patch
>
>
> Currently, any router seems to exist in the Router Information eternally.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
