[IMPALA-3702] Identify crashed Impala queries

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: impala 2.3
• Component/s: Backend
• Assignee: Unassigned
• Reporter: Matyas Orhidi
• Created: 09/Jun/16 12:26
• Updated: 09/Jun/16 16:31
• Resolved: 09/Jun/16 16:30

Description

It is really hard to determine which query forced an impala daemon to crash in a larger cluster, since the Impala ERROR logs contain no query ID and the crashed queries does not show up in Cloudera Manager. A query id in the ERROR log would be very useful in such cases:

E0516 08:59:51.066875 55392 logging.cc:120] stderr will be logged to this file.
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::gregorian::bad_year> >'
what(): Year is out of valid range: 1400..10000

Issue Links

• duplicates: IMPALA-3703 Store query context in thread-local variables and use in crash reports
• relates to: IMPALA-2184 Codegen does not catch exceptions in FROM_UNIXTIME()