[
https://issues.apache.org/jira/browse/HDFS-14669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16898689#comment-16898689
]
Ayush Saxena commented on HDFS-14669:
-------------------------------------
Addendum is only till that JIRA isn’t released. I have no background of what
was the context then, I know the waitFor will abstract the actual exception
but it adds a ability to counter fixed time sleeps, everything got its pros and
cons. I don’t deny the fact that there are improvements to the present logic
possible, but whether required or not, But removing it without any agreement
from the guys there for what we are fixing here isn’t something I can’t alone
give a nod to it. I am happy enough with v4 (if JENKINS stays happy too)
Regarding the doubts or fate of HDFS-13819, [~elgoiri] any opinions further?
> TestDirectoryScanner#testDirectoryScannerInFederatedCluster fails
> intermittently in trunk
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-14669
> URL: https://issues.apache.org/jira/browse/HDFS-14669
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 3.2.0
> Environment: env free
> Reporter: qiang Liu
> Assignee: qiang Liu
> Priority: Minor
> Labels: scanner, test
> Attachments: HDFS-14669-trunk-001.patch, HDFS-14669-trunk.002.patch,
> HDFS-14669-trunk.003.patch, HDFS-14669-trunk.004.patch
>
>
> org.apache.hadoop.hdfs.server.datanode.TestDirectoryScanner#testDirectoryScannerInFederatedCluster
> radomlly Failes because of write files of the same name, meaning intent to
> write 2 files but 2 files are the same name, witch cause a race condition of
> datanode delete block and the scan action count block.
>
> Ref ::
> [https://builds.apache.org/job/hadoop-qbt-trunk-java8-linux-x86/1207/testReport/junit/org.apache.hadoop.hdfs.server.datanode/TestDirectoryScanner/testDirectoryScannerInFederatedCluster/]
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
