You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/21 07:32:00 UTC
[jira] [Commented] (IMPALA-11341) Print error log files when data-loading fails
[ https://issues.apache.org/jira/browse/IMPALA-11341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556701#comment-17556701 ]
ASF subversion and git services commented on IMPALA-11341:
----------------------------------------------------------
Commit 66cde5ba8f707e61b1b46dabe114819de8b4f75d in impala's branch refs/heads/master from stiga-huang
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=66cde5ba8 ]
IMPALA-11341: Print error log files when data-loading fails
run-step will print the last 50 lines of the log file when the step
fails. However, the data-loading log file just shows the log file names
of the failed sql files. We still need to manually look into them for
more details.
This patch extends run-step to also print the last 100 lines of such log
files.
Tested locally by stopping impala cluster to mimic an error state and
run these in my terminal:
source testdata/bin/run-step.sh
export LOG_DIR=tmp
run-step "Loading functional-query data" load-functional-query.log bin/load-data.py -e exhaustive -w functional-query
Change-Id: I771b4b74e00d89a3cc85f26b8b1da66c3dd66304
Reviewed-on: http://gerrit.cloudera.org:8080/18597
Reviewed-by: Quanlong Huang <hu...@gmail.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> Print error log files when data-loading fails
> ---------------------------------------------
>
> Key: IMPALA-11341
> URL: https://issues.apache.org/jira/browse/IMPALA-11341
> Project: IMPALA
> Issue Type: Task
> Components: Infrastructure
> Reporter: Quanlong Huang
> Assignee: Quanlong Huang
> Priority: Major
>
> When the data-loading phase fails, we see console ouputs like
> {noformat}
> 05:04:02 Beginning execution of hive SQL: /home/ubuntu/Impala/logs/data_loading/sql/functional/load-functional-query-exhaustive-hive-generated-rc-def-block.sql
> 05:05:34 Finished execution of hive SQL: /home/ubuntu/Impala/logs/data_loading/sql/functional/load-functional-query-exhaustive-hive-generated-seq-bzip-record.sql
> 05:05:34 Error executing hive SQL: /home/ubuntu/Impala/logs/data_loading/sql/functional/load-functional-query-exhaustive-hive-generated-text-def-block.sql See: /home/ubuntu/Impala/logs/data_loading/sql/functional/load-functional-query-exhaustive-hive-generated-text-def-block.sql.log
> 05:05:34 Beginning execution of hive SQL: /home/ubuntu/Impala/logs/data_loading/sql/functional/load-functional-query-exhaustive-hive-generated-seq-bzip-block.sql
> 05:05:34 Beginning execution of hive SQL: /home/ubuntu/Impala/logs/data_loading/sql/functional/load-functional-query-exhaustive-hive-generated-seq-gzip-record.sql
> Background task Loading functional-query data (pid 14732) failed.
> ERROR in /home/ubuntu/Impala/testdata/bin/create-load-data.sh at line 85: fi
> Generated: /home/ubuntu/Impala/logs/extra_junit_xml_logs/generate_junitxml.buildall.create-load-data.20220607_05_05_34.xml
> {noformat}
> We still need to download the Jenkins log file and extract the tarball to get load-functional-query-exhaustive-hive-generated-text-def-block.sql.log. It'd be helpful if we can print its last 50 lines as well.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org