[jira] [Commented] (HDFS-16200) Improve NameNode failover

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot commented on HDFS-16200:
---------------------------------------

github-actions[bot] commented on PR #3364:
URL: https://github.com/apache/hadoop/pull/3364#issuecomment-3573252760

   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.
   If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again.
   Thanks all for your contribution.




> Improve NameNode failover
> -------------------------
>
>                 Key: HDFS-16200
>                 URL: https://issues.apache.org/jira/browse/HDFS-16200
>             Project: Hadoop HDFS
>          Issue Type: Task
>          Components: namenode
>    Affects Versions: 2.8.2
>            Reporter: Aihua Xu
>            Assignee: Aihua Xu
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> In a busy cluster, we are noticing the NameNode failover takes longer time (over 10 minutes) and it causes cluster down time during the time period.
> One bottleneck locates in resolving the client host's topology when the cluster is not colocated with the computing hosts. NameNode resolves the client host's topology and uses it to sort the hosts where the blocks locate in. Such topology will be cached so the next access will be efficient, while if the standby NameNode is newly restarted, then all the client hosts, e.g., YARN hosts need to be resolved.
> Solutions can be: 1) we can expose an API in DFSAdmin to load topology cache, or 2) we can add a new configuration in HDFS cluster to skip resolving topology for non-colocated HDFS cluster. Since client hosts and HDFS hosts are not colocated, it's unnecessary to sort the DataNodes for the clients.     



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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