[
https://issues.apache.org/jira/browse/HDFS-2851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13195786#comment-13195786
]
Uma Maheswara Rao G commented on HDFS-2851:
-------------------------------------------
I am thinking about this issue. When switch happens currently we will mark the
blocks as stale for the nodes. Whenever process transitioned from
standbyToActive, if we trigger one block report, then that particular node
status will be marked as normal. So, it will process the OverReplicated blocks
normally instead of postponing till next block report.
Todd, is there any design constraint we have currently to trigger block report
when NN switched from standby to active state?
> HA: After Balancer runs, usedSpace is not balancing correctly.
> --------------------------------------------------------------
>
> Key: HDFS-2851
> URL: https://issues.apache.org/jira/browse/HDFS-2851
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: balancer, data-node, ha, name-node
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Uma Maheswara Rao G
> Assignee: Uma Maheswara Rao G
> Attachments: HDFS-2851-HDFS-1623-Test.patch
>
>
> After Balancer runs, usedSpace is not balancing correctly.
> {code}
> java.util.concurrent.TimeoutException: Cluster failed to reached expected
> values of totalSpace (current: 1500, expected: 1500), or usedSpace (current:
> 390, expected: 300), in more than 20000 msec.
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancer.waitForHeartBeat(TestBalancer.java:233)
> at
> org.apache.hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes.testBalancerWithHANameNodes(TestBalancerWithHANameNodes.java:99)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
