-
Notifications
You must be signed in to change notification settings - Fork 9.2k
HDFS-16200: Improve NameNode failover #3364
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
💔 -1 overall
This message was automatically generated. |
…ing topolgy for client hosts Summary: This is to didable resolving topology for write traffic. When addBlock() is called, topology info will not be used to choose the DataNodes when dfs.disable.datanode.topology.sort is set to true. Test Plan: unit test Reviewers: O2125 User ekanth: Add reviewers, O2121 Project Hadoop-HDFS Dev: Add blocking reviewers, jingzhao, qifan Reviewed By: O2121 Project Hadoop-HDFS Dev: Add blocking reviewers, jingzhao, qifan Subscribers: O2133 Project Data Foundation - Hadoop Ecosystem: Add subscribers, O2131 Project Hadoop-HDFS Dev: Add subscribers JIRA Issues: HDFS-1732 Differential Revision: https://code.uberinternal.com/D6522861
|
💔 -1 overall
This message was automatically generated. |
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
This patch adds a configuration to skip resolving the topology for the client hosts, e.g., YARN hosts. Such topology info is useful in colocated environment but not in non-colocated env.
How was this patch tested?
unit test