[
https://issues.apache.org/jira/browse/HDFS-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16739027#comment-16739027
]
Fengnan Li commented on HDFS-14118:
-----------------------------------
I agree it will affect all of the Namenode clients, but in a good way in the
long run. There are only a couple of cases:
For current HDFS clients with or without router:
1) they want to upgrade with this single domain name, which is great, what they
need to change is their config file + hadoop version.
2) they don't want to upgrade, they can still keep their original config since
we won't change the namenode machine, the HDFS namenode change frequency is
also pretty low. Once we want to make the machine switch, it is a good time to
sell this approach that once they upgrade the client, they don't need to change
their code or config anymore, and always use the same domain name after one
time effort.
Overall, since it is only a client side change, clients with and without change
can both work, which makes the onboarding a lot easier.
> 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: [email protected]
For additional commands, e-mail: [email protected]
