[
https://issues.apache.org/jira/browse/HDFS-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706699#comment-16706699
]
Surendra Singh Lilhore commented on HDFS-14118:
-----------------------------------------------
{quote}Clients will need to know about routers to talk to the HDFS cluster
(obviously), and having routers updating (adding/removing) will have to make
every client change, which is a painful process.
{quote}
[~linyiqun], HDFS-14079 is for router admin RPC, but I think [~fengnanli] is
talking about normal file system RPC for router.
{quote}Another way is to have the client do the normal connecting/failover
after they get the list of routers
{quote}
[~fengnanli], currenlty it is doing the same right ?
> RBF: Use DNS to help resolve routers
> ------------------------------------
>
> Key: HDFS-14118
> URL: https://issues.apache.org/jira/browse/HDFS-14118
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Fengnan Li
> Assignee: Fengnan Li
> Priority: Major
>
> Clients will need to know about routers to talk to the HDFS cluster
> (obviously), and having routers updating (adding/removing) will have to make
> every client change, which is a painful process.
> DNS can be used here to resolve the single domain name clients knows to a
> list of routers in the current config. However, DNS won't be able to consider
> only resolving to the working router based on certain health thresholds.
> There are some ways about how this can be solved. One way is to have a
> separate script to regularly check the status of the router and update the
> DNS records if a router fails the health thresholds. In this way, security
> might be carefully considered for this way. Another way is to have the client
> do the normal connecting/failover after they get the list of routers, which
> requires the change of current failover proxy provider.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
