[
https://issues.apache.org/jira/browse/HIVE-13520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242560#comment-15242560
]
Siddharth Seth commented on HIVE-13520:
---------------------------------------
HIVE-13507 adds some logging which should help figure out a better value. If
not 45 minutes, do you think 1 hour is reasonable ?
15 tests running for 45 minutes seems like a lot - especially when entire runs
can complete in less than 2 hours (<1.5 hour test runtime). This is mainly to
prevent a bad test from causing the entire test-run to take 3+ hours.
HostExecutor.java actually writes out a file based on patch-exec.vm - so I
won't be surprised if this works without a restart.
As with HIVE-13505, lets get this committed, and monitor a couple of runs to
see what happens.
> Don't allow any test to run for longer than 45minutes in the ptest setup
> ------------------------------------------------------------------------
>
> Key: HIVE-13520
> URL: https://issues.apache.org/jira/browse/HIVE-13520
> Project: Hive
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: HIVE-13520.01.txt, HIVE-13520.02.txt
>
>
> Current timeout for batches is 2hours. This needs to be lowered. 1hour may be
> too much as well. We can start with this, and reduce timeouts further.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
