[
https://issues.apache.org/jira/browse/HDFS-11384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15949593#comment-15949593
]
Vinitha Reddy Gankidi commented on HDFS-11384:
----------------------------------------------
Two other approaches to fix this:
1. In {{getBlockList()}} Dispatcher fetches the blocks belonging to a
particular DN from the NN. And then it moves those blocks from the source DN to
the target DN. Dispatcher can instead get the blocks directly from the
particular DN. This makes {{getBlocksList()}} a distributed operation and
doesn't impact any specific node.
2. Dispatcher can fetch the blocks from the Standby NN instead of the active.
Balancer should be able to tolerate reasonable degree of staleness.
> Add option for balancer to disperse getBlocks calls to avoid NameNode's
> rpc.CallQueueLength spike
> -------------------------------------------------------------------------------------------------
>
> Key: HDFS-11384
> URL: https://issues.apache.org/jira/browse/HDFS-11384
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: balancer & mover
> Affects Versions: 2.7.3
> Reporter: yunjiong zhao
> Assignee: yunjiong zhao
> Attachments: balancer.day.png, balancer.week.png,
> HDFS-11384.001.patch, HDFS-11384.002.patch
>
>
> When running balancer on hadoop cluster which have more than 3000 Datanodes
> will cause NameNode's rpc.CallQueueLength spike. We observed this situation
> could cause Hbase cluster failure due to RegionServer's WAL timeout.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
