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

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Impala 2.7.0
• Fix Version/s: Impala 2.11.0
• Component/s: Backend
• Labels: breakpad observability supportability
• Target Version: Product Backlog
• Assignee: Zoltán Borók-Nagy
• Reporter: Tim Armstrong
• Created: 09/Jun/16 16:27
• Updated: 14/Mar/18 19:11
• Resolved: 03/Jan/18 10:48

Description

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

Issue Links

• is duplicated by: IMPALA-3702 Identify crashed Impala queries
• is related to: IMPALA-4200 Collection of things to add to Minidump files
• relates to: IMPALA-6664 Tag log statements with query-ids