hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "xuzq (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-14728) RBF:GetDatanodeReport causes a large GC pressure on the NameNodes
Date Tue, 13 Aug 2019 10:56:00 GMT

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

xuzq commented on HDFS-14728:
-----------------------------

Thanks [~zhangchen].

I think we can cache the datanode report in RouterRpcServer like NamenodeBeanMetrics.

NamenodeBeanMetrics and RBFMetrics can get datanode report from the cache in RouterRpcServer.

> RBF:GetDatanodeReport causes a large GC pressure on the NameNodes
> -----------------------------------------------------------------
>
>                 Key: HDFS-14728
>                 URL: https://issues.apache.org/jira/browse/HDFS-14728
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: rbf
>            Reporter: xuzq
>            Priority: Major
>
> When a cluster contains millions of DNs, *GetDatanodeReport* is pretty expensive, and
it will cause a large GC pressure on NameNode.
> When multiple NSs share the millions DNs by federation and the router listens to the
NSs, the problem will be more serious.
> All the NSs will be GC at the same time.
> RBF should cache the datanode report informations and have an option to disable the cache.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
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