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-14728) RBF: GetDatanodeReport causes a large GC pressure on the NameNodes
Date Thu, 15 Aug 2019 17:50:00 GMT

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

Íñigo Goiri commented on HDFS-14728:

The checkstyle complain might point into the good direction... this constructor is getting
way too long.
Can we do all this init in a function called {{initDNReportCache()}} or similar?

> 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
>            Assignee: xuzq
>            Priority: Major
>         Attachments: HDFS-14728-trunk-001.patch, HDFS-14728-trunk-002.patch, HDFS-14728-trunk-003.patch,
HDFS-14728-trunk-004.patch, HDFS-14728-trunk-005.patch
> 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

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

View raw message