[IMPALA-5651] Investigate cheaper stack trace printing mechanism

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Later
• Affects Version/s: Impala 2.9.0
• Component/s: Backend
• Labels: observability performance
• Target Version: Product Backlog
• Epic Color: ghx-label-3
• Assignee: Unassigned
• Reporter: Matthew Jacobs
• Created: 12/Jul/17 15:34
• Updated: 07/Feb/23 11:14
• Resolved: 21/Jan/20 21:01

Description

In IMPALA-5275, mmokhtar identified several code paths where Status() was printing expensive stack traces in performance sensitive code. That JIRA is being used to track fixing those individual cases, but we should also investigate if we can print stack traces in a more efficient manner in general.