[ 
https://issues.apache.org/jira/browse/HIVE-27295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-27295:
--------------------------------
    Description: 
1. While waiting for docker container to start properly, we should print the 
output of docker logs command in every loop, otherwise we can miss important 
information if the docker container is oom killed in the meantime. Not to 
mention the fact that we're currently not logging the output at all in case of 
an error:
https://github.com/apache/hive/blob/59058c65457fb7ab9d8575a555034e6633962661/itests/util/src/main/java/org/apache/hadoop/hive/ql/externalDB/AbstractExternalDB.java#L125-L127

2. We can include the output for docker events in the logs in case of an error 
(like: oom killed container), which might contain useful information.

3. Consider adding a [--memory 
option|https://docs.docker.com/config/containers/resource_constraints/] to the 
docker run command with a reasonable value to make the RDBMS docker image 
running process stable and independent from system settings.

> Improve docker logging in AbstractExternalDB
> --------------------------------------------
>
>                 Key: HIVE-27295
>                 URL: https://issues.apache.org/jira/browse/HIVE-27295
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>
> 1. While waiting for docker container to start properly, we should print the 
> output of docker logs command in every loop, otherwise we can miss important 
> information if the docker container is oom killed in the meantime. Not to 
> mention the fact that we're currently not logging the output at all in case 
> of an error:
> https://github.com/apache/hive/blob/59058c65457fb7ab9d8575a555034e6633962661/itests/util/src/main/java/org/apache/hadoop/hive/ql/externalDB/AbstractExternalDB.java#L125-L127
> 2. We can include the output for docker events in the logs in case of an 
> error (like: oom killed container), which might contain useful information.
> 3. Consider adding a [--memory 
> option|https://docs.docker.com/config/containers/resource_constraints/] to 
> the docker run command with a reasonable value to make the RDBMS docker image 
> running process stable and independent from system settings.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to