[
https://issues.apache.org/jira/browse/HDFS-13908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620811#comment-16620811
]
Íñigo Goiri commented on HDFS-13908:
------------------------------------
You are right, the case is the opposite and it is to make sure it does not come
back up.
Ideally this should be done trying to wait for the scenario that would trigger
the DN to come back up.
Anyway that's different to what we are solving here.
Committing soon.
Feel free to open a new JIRA to tackle the next sleep(10).
BTW, I went through the report and there are a bunch of tests that take +2
minutes, I didn't see anything obvious that could be done.
> TestDataNodeMultipleRegistrations is flaky
> ------------------------------------------
>
> Key: HDFS-13908
> URL: https://issues.apache.org/jira/browse/HDFS-13908
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: Íñigo Goiri
> Assignee: Ayush Saxena
> Priority: Major
> Attachments: Above Timeout.rar, HDFS-13908-01.patch,
> HDFS-13908-02.patch, HDFS-13908-03.patch, HDFS-13908-04.patch, Within
> TImeout.rar
>
>
> We have seen this issue in multiple runs:
> https://builds.apache.org/job/PreCommit-HADOOP-Build/15146/testReport/org.apache.hadoop.hdfs.server.datanode/TestDataNodeMultipleRegistrations/testClusterIdMismatchAtStartupWithHA/
> https://builds.apache.org/job/PreCommit-HADOOP-Build/15116/testReport/org.apache.hadoop.hdfs.server.datanode/TestDataNodeMultipleRegistrations/testDNWithInvalidStorageWithHA/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
