[
https://issues.apache.org/jira/browse/IMPALA-8680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408313#comment-17408313
]
ASF subversion and git services commented on IMPALA-8680:
---------------------------------------------------------
Commit 45d3eddc056bc28ee43efa6307cd673062936a41 in impala's branch
refs/heads/master from Zoltan Garaguly
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=45d3edd ]
IMPALA-8680: Docker-based tests fail to archive the minicluster component logs
Inside docker container copy logs of cluster components hdfs, yarn, kudu
from folder testdata/cluster/cdh<version-number>/node-<node-id>/var/log/
to folder logs/cluster/
Testing:
- running docker-based tests and checked that minicluster logs are preserved
and archived
- test if minicluster logs get copied also in case when something gets wrong
during build
Change-Id: I23e25d42992cec47c593dc388bcf0bcef828c05e
Reviewed-on: http://gerrit.cloudera.org:8080/15898
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Docker-based tests fail to archive the minicluster component logs
> -----------------------------------------------------------------
>
> Key: IMPALA-8680
> URL: https://issues.apache.org/jira/browse/IMPALA-8680
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Laszlo Gaal
> Assignee: Zoltán Garaguly
> Priority: Major
>
> When Docker-based tests (docker/test-with-docker.py) are executed in a
> Jenkins environment, all the logs are archived at the end of the run – at
> least that's the intention. However, the logs for minicluster components,
> namely Kudu, are lost, because the script does not follow the symlink into
> the minicluster node directories, it just archives the symlink files. This
> leads to a loss of logs, making troubleshooting harder.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
