hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Íñigo Goiri (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HDFS-14118) Support using DNS to resolve nameservices to IP addresses
Date Sat, 23 Feb 2019 17:45:00 GMT

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

Íñigo Goiri commented on HDFS-14118:
------------------------------------

[^HDFS-14118.024.patch] LGTM.
The failed unit tests are unrelated (pretty flaky in general).
+1

[~yzhangal] go ahead with the commit; thanks for the review.
Thanks [~fengnanli] for the patch!

> Support using DNS to resolve nameservices to IP addresses
> ---------------------------------------------------------
>
>                 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 design doc_ Single domain name for clients
- Google Docs-1.pdf, HDFS design doc_ Single domain name for clients - Google Docs.pdf, 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.020.patch, HDFS-14118.021.patch,
HDFS-14118.022.patch, HDFS-14118.023.patch, HDFS-14118.024.patch, HDFS-14118.patch
>
>
> In router based federation (RBF), clients will need to know about routers to talk to
the HDFS cluster (obviously), and having routers updating (adding/removing) will have to make
config change in every client, 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.
> See the attached design document for details about the proposed solution.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message