Lars Volker created IMPALA-8610:
-----------------------------------

             Summary: Log rotation can fail 
gerrit-verify-dryrun/ubuntu-16.04-from-scratch jobs
                 Key: IMPALA-8610
                 URL: https://issues.apache.org/jira/browse/IMPALA-8610
             Project: IMPALA
          Issue Type: Bug
          Components: jenkins, Infrastructure
            Reporter: Lars Volker
            Assignee: Lars Volker


It seems that otherwise successful runs of {{ubuntu-16.04-from-scratch}} can 
fail at the end when copying log files in the end. If the impalads are still 
running, they can rotate a logfile while {{cp}} tries to copy it, which results 
in output like this ([affected 
job|https://jenkins.impala.io/job/ubuntu-16.04-from-scratch/6027/console]):

{noformat}
00:24:28 + cp -r -L /home/ubuntu/Impala/logs /home/ubuntu/Impala/logs_static
00:24:37 cp: cannot stat 
'/home/ubuntu/Impala/logs/cluster/impalad.ip-172-31-19-200.ubuntu.log.WARNING.20190601-072315.102026':
 No such file or directory
00:24:37 cp: cannot stat 
'/home/ubuntu/Impala/logs/cluster/impalad.ip-172-31-19-200.ubuntu.log.WARNING.20190601-072304.100810':
 No such file or directory
00:24:37 cp: cannot stat 
'/home/ubuntu/Impala/logs/cluster/impalad.ip-172-31-19-200.ubuntu.log.WARNING.20190601-072315.102023':
 No such file or directory
{noformat}

Note that the script is currently configured in Jenkins to run in a shell with 
{{-e}} and that a successful run contains additional lines after the {{cp}} 
command:

{noformat}
04:16:18 + cp -r -L /home/ubuntu/Impala/logs /home/ubuntu/Impala/logs_static
04:16:21 + rm -f /tmp/git-err-ksiZp.log
{noformat}

As a fix we should kill all daemons before copying the files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to