[
https://issues.apache.org/jira/browse/IMPALA-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17949807#comment-17949807
]
ASF subversion and git services commented on IMPALA-14000:
----------------------------------------------------------
Commit 2f9abc4e80b5c7dd71d42ad839820b556ba071cd in impala's branch
refs/heads/master from stiga-huang
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2f9abc4e8 ]
IMPALA-14000: Dump jstacks first in dump-stacktraces.sh
bin/dump-stacktraces.sh collects pstack and jstack of the cluster. It's
used when some tests time out. Collecting pstacks might take long and
fail in the middle, causing jstacks not being collected. This changes
the script to collect jstacks first.
Also adds -c to the "thread apply all bt" gdb command to continue past
an error.
Change-Id: I8f610ee4d4934fe950a9f56cf74a7e76e5d63651
Reviewed-on: http://gerrit.cloudera.org:8080/22826
Reviewed-by: Daniel Becker <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> dump-stacktraces.sh might not dump the jstacks
> ----------------------------------------------
>
> Key: IMPALA-14000
> URL: https://issues.apache.org/jira/browse/IMPALA-14000
> Project: IMPALA
> Issue Type: Bug
> Components: Infrastructure
> Reporter: Quanlong Huang
> Assignee: Quanlong Huang
> Priority: Major
>
> In bin/dump-stacktraces.sh, we dump the pstack before jstack for catalogd and
> impalads. pstack could take long and if it fails, the jstack is missing:
> {code:bash}
> collect_gdb_backtraces catalogd $CATALOGD_PID && \
> collect_jstacks catalogd $CATALOGD_PID &
> {code}
> Consider reorder them to take jstack first.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
