You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Zoram Thanga (JIRA)" <ji...@apache.org> on 2019/03/28 18:23:00 UTC
[jira] [Resolved] (IMPALA-7508) Add Impala GDB commands to find
fragment instances and queries in a core file
[ https://issues.apache.org/jira/browse/IMPALA-7508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zoram Thanga resolved IMPALA-7508.
----------------------------------
Resolution: Fixed
Resolving now.
> Add Impala GDB commands to find fragment instances and queries in a core file
> -----------------------------------------------------------------------------
>
> Key: IMPALA-7508
> URL: https://issues.apache.org/jira/browse/IMPALA-7508
> Project: IMPALA
> Issue Type: Improvement
> Components: Infrastructure
> Affects Versions: Impala 2.12.0, Impala 3.1.0
> Reporter: Zoram Thanga
> Assignee: Zoram Thanga
> Priority: Minor
> Labels: debugging, supportability
>
> Introduce a Python GDB module, and a couple of commands that helps to find queries and fragment instances that are executing in an impalad at the time the daemon crashes.
> One hopes that folks will keep enhancing the module by adding new and useful GDB commands to aid debugging impalad core dumps.
> The initial patch has these:
> {noformat}
> (gdb) source impala-gdb.py
> (gdb) find-query-ids
> f74c863dff66a34d:1d983cc300000000
> 364525e12495932b:73f5dd0200000000
> bc4a3eec25481981:edda04b800000000
> (gdb) find-fragment-instances
> Fragment Instance Id Thread IDs
> 364525e12495932b:73f5dd02000000a2 [69]
> 364525e12495932b:73f5dd0200000171 [196, 136]
> bc4a3eec25481981:edda04b8000001a8 [252, 237, 206]
> f74c863dff66a34d:1d983cc30000009b [200, 14, 13, 12, 6, 5, 3, 2]
> f74c863dff66a34d:1d983cc30000013a [4]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)