[
https://issues.apache.org/jira/browse/HIVE-29462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
László Bodor updated HIVE-29462:
--------------------------------
Description: It happens quite often that we investigate docker timeout
issues, when we might want to know how much time does it take to start and init
containers under normal circumstances (when unit test passes), in which case we
should be able to simply grep in successful test logs to see that to get quick
answers on: a) is it always close to the timeout, just passes accidentally, or
b) is it always a few seconds just something happened now. This would help us
make better decisions about whether to increase timeouts in the future. (was:
It happens quite often that we investigate docker timeout issues, when we might
want to know how much time does it take to start and init containers under
normal circumstances (when unit test passes), in which case we should be able
to simply grep in successful test logs to see that to get quick answers on: a)
is it always close to the timeout, just passes accidentally, or b) is it always
a few seconds just something happened now. This would help us make better
decisions about possible increasing timeouts in the future.)
> Log start/init times for Docker, external DB resources
> ------------------------------------------------------
>
> Key: HIVE-29462
> URL: https://issues.apache.org/jira/browse/HIVE-29462
> Project: Hive
> Issue Type: Improvement
> Reporter: László Bodor
> Assignee: László Bodor
> Priority: Major
>
> It happens quite often that we investigate docker timeout issues, when we
> might want to know how much time does it take to start and init containers
> under normal circumstances (when unit test passes), in which case we should
> be able to simply grep in successful test logs to see that to get quick
> answers on: a) is it always close to the timeout, just passes accidentally,
> or b) is it always a few seconds just something happened now. This would help
> us make better decisions about whether to increase timeouts in the future.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
