[
https://issues.apache.org/jira/browse/HDFS-14118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773337#comment-16773337
]
Yongjun Zhang edited comment on HDFS-14118 at 2/20/19 7:58 PM:
---------------------------------------------------------------
Hi [~fengnanli],
For the benefit of the community, would you please provide a one or two page
description about this feature and attach to the jira:
1. Issue to address, case scenarios, better with an example(s)
2. You mentioned multiple approaches in the jira description, which approach
you implemented? Please try to provide a bit detail about each approach, pros
and cons. Seems you implemented "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.". But the jira description is
not clear about that.
3. How to use this feature (class to provide, configurations to set etc)
4. Some concrete use scenario examples to explain how your solution works, and
how people may extend it to address new need (possible new/different class
implementation)
This will help reviewers, users, and future documentation.
Thanks.
was (Author: yzhangal):
Hi [~fengnanli],
For the benefit of the community, would you please provide a one or two page
description about this feature and attach to the jira:
1. Issue to address, case scenarios, better with an example(s)
2. You mentioned multiple approaches in the jira description, which approach
you implemented? Please try to provide a bit detail about each approach, pros
and cons. Seems you implemented "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.". But the jira description is
not clear about that.
3. Some concrete use scenario examples to explain how your solution works?
Thanks.
> Use DNS to resolve Namenodes and Routers
> ----------------------------------------
>
> Key: HDFS-14118
> URL: https://issues.apache.org/jira/browse/HDFS-14118
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Fengnan Li
> Assignee: Fengnan Li
> Priority: Major
> Attachments: DNS testing log, HDFS-14118.001.patch,
> HDFS-14118.002.patch, HDFS-14118.003.patch, HDFS-14118.004.patch,
> HDFS-14118.005.patch, HDFS-14118.006.patch, HDFS-14118.007.patch,
> HDFS-14118.008.patch, HDFS-14118.009.patch, HDFS-14118.010.patch,
> HDFS-14118.011.patch, HDFS-14118.012.patch, HDFS-14118.013.patch,
> HDFS-14118.014.patch, HDFS-14118.015.patch, HDFS-14118.016.patch,
> HDFS-14118.017.patch, HDFS-14118.018.patch, HDFS-14118.019.patch,
> 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
