[jira] [Closed] (IMPALA-3703) Store query context in thread-local variables and use in crash reports

["Zoltán Borók-Nagy (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-3703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zoltán Borók-Nagy closed IMPALA-3703.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.11.0

Fixed in https://github.com/apache/impala/commit/8047b1dcb421994e67e6db412529159dde2f40b5

> Store query context in thread-local variables and use in crash reports
> ----------------------------------------------------------------------
>
>                 Key: IMPALA-3703
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3703
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.7.0
>            Reporter: Tim Armstrong
>            Assignee: Zoltán Borók-Nagy
>            Priority: Minor
>              Labels: breakpad, observability, supportability
>             Fix For: Impala 2.11.0
>
>
> If Impala crashes or hits some kind of unexpected error, it's useful to know what query the thread that crashed belonged to and be able to easily find the state of the query.
> We should store some state in thread-local variables and then make sure that it can be found in the event of a crash.
> We should:
> * Store a pointer to the RuntimeState object in a thread-local variable
> * Report basic info in the breakpad crash report and logs if there is a crash
> ** Query ID
> ** Fragment instance ID
> ** Thread Name
> ** ???
> * Document how to find the thread-local variables in coredumps



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)