[
https://issues.apache.org/jira/browse/HDFS-9776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17219951#comment-17219951
]
Ahmed Hussein commented on HDFS-9776:
-------------------------------------
The link is not available anymore. The lira was filed several years ago;
therefore, I am not sure we can rely on the same assessment.
In the attached log, I see :
{code:bash}
2020-10-22 20:46:05,889 [IPC Server handler 0 on default port 44039] INFO
blockmanagement.BlockPlacementPolicy
(BlockPlacementPolicyDefault.java:chooseRandom(897)) - Not enough replicas was
chosen. Reason: {NODE_TOO_BUSY=1}
{code}
Perhaps the unit test cane less flaky if we add
{code:java}
conf.setBoolean(DFSConfigKeys.DFS_NAMENODE_REDUNDANCY_CONSIDERLOAD_KEY, false);
{code}
> TestHAAppend#testMultipleAppendsDuringCatchupTailing is flaky
> -------------------------------------------------------------
>
> Key: HDFS-9776
> URL: https://issues.apache.org/jira/browse/HDFS-9776
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Vinayakumar B
> Priority: Major
> Attachments: TestHAAppend.testMultipleAppendsDuringCatchupTailing.log
>
>
> Initial analysys of Recent test failure in
> {{TestHAAppend#testMultipleAppendsDuringCatchupTailing}}
> [here|https://builds.apache.org/job/PreCommit-HDFS-Build/14420/testReport/org.apache.hadoop.hdfs.server.namenode.ha/TestHAAppend/testMultipleAppendsDuringCatchupTailing/]
>
> has found that, if the Active NameNode goes down immediately after truncate
> operation, but before BlockRecovery command sent to datanode,
> Then this block will never be truncated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
