[ 
https://issues.apache.org/jira/browse/HDFS-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738569#comment-16738569
 ] 

Íñigo Goiri edited comment on HDFS-14118 at 1/9/19 7:23 PM:
------------------------------------------------------------

{quote}
One thing I don't understand in your comment for HDFS-13312 is that it will 
affect a lot of components. Do you refer to that DN will need this approach as 
well?
{quote}

I was referring to clients contacting Namenodes.
This would affect them and that's why I'm proposing to move it out of RBF.
However, this approach could also be used by Datanodes to contact Namenodes.
I would focus on the clients for now.


was (Author: elgoiri):
{quote}
One thing I don't understand in your comment for HDFS-13312 is that it will 
affect a lot of components. Do you refer to that DN will need this approach as 
well?
{quote}

I was referring to clients contacting Namenodes.
This would affect them and that's why I'm proposing to move it out of RBF.

> 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
>         Attachments: HDFS-14118.patch
>
>
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to