[
https://issues.apache.org/jira/browse/HUDI-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sagar Sumit updated HUDI-3023:
------------------------------
Description: Recently, we encountered an issue in integ tests where
namenode was not ready yet to receive connections (still in safemode) and hdfs
commands in ITTestHoodieDemo setup were not succeeeding. The namenode typically
takes some time (2-3 minutes) to come up. While adding a delay is a workaround,
it would be better to execute this test after others like
ITTestHoodieSyncCommand and ITTestHoodieSanity. With JUnit 5.8 we can order
test classes and as we already have a working patch for upgrading junit
(https://github.com/apache/hudi/pull/3748) we should consider ficing the order
to avoid flakiness. (was: Recently, we encountered an issue in integ tests
where namenode was not ready yet to receive connections (still in safemode) and
hdfs commands in ITTestHoodieDemo setup were not succeeeding. The namenode
typically takes some time (2-3 minutes) to come up. While adding a delay is a
workaround, it would be better to execute this test after others like
ITTestHoodieSyncCommand and ITTestHoodieSanity.)
> Fix order of tests
> ------------------
>
> Key: HUDI-3023
> URL: https://issues.apache.org/jira/browse/HUDI-3023
> Project: Apache Hudi
> Issue Type: Sub-task
> Reporter: Sagar Sumit
> Assignee: Sagar Sumit
> Priority: Major
>
> Recently, we encountered an issue in integ tests where namenode was not ready
> yet to receive connections (still in safemode) and hdfs commands in
> ITTestHoodieDemo setup were not succeeeding. The namenode typically takes
> some time (2-3 minutes) to come up. While adding a delay is a workaround, it
> would be better to execute this test after others like
> ITTestHoodieSyncCommand and ITTestHoodieSanity. With JUnit 5.8 we can order
> test classes and as we already have a working patch for upgrading junit
> (https://github.com/apache/hudi/pull/3748) we should consider ficing the
> order to avoid flakiness.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
