[
https://issues.apache.org/jira/browse/HIVE-25714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445865#comment-17445865
]
Stamatis Zampetakis commented on HIVE-25714:
--------------------------------------------
Actually there is a busy-wait loop when launching the containers which waits
for one sec ({{Thread.sleep(1000);}}) before asking again for logs.
I agree that including some log lines could help us understand better what the
problem is. We could actually do it only when the container fails to start. I
will do the modif and launch again the flaky checker.
> Some tests are flaky because docker is not able to start in 5 seconds
> ---------------------------------------------------------------------
>
> Key: HIVE-25714
> URL: https://issues.apache.org/jira/browse/HIVE-25714
> Project: Hive
> Issue Type: Improvement
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
>
> there are some testruns failing with; and on the test site multiple pods are
> running in parallel - its not an ideal environment for tight deadlines
> {code}
> Unexpected exception java.lang.RuntimeException: Process docker failed to run
> in 5 seconds
> at
> org.apache.hadoop.hive.ql.externalDB.AbstractExternalDB.runCmd(AbstractExternalDB.java:92)
> at
> org.apache.hadoop.hive.ql.externalDB.AbstractExternalDB.launchDockerContainer(AbstractExternalDB.java:123)
> at
> org.apache.hadoop.hive.ql.qoption.QTestDatabaseHandler.beforeTest(QTestDatabaseHandler.java:111)
> at
> org.apache.hadoop.hive.ql.qoption.QTestOptionDispatcher.beforeTest(QTestOptionDispatcher.java:79)
> {code}
> http://ci.hive.apache.org/job/hive-precommit/job/PR-1674/4/testReport/junit/org.apache.hadoop.hive.cli.split19/TestMiniLlapLocalCliDriver/Testing___split_14___PostProcess___testCliDriver_qt_database_all_/
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
