impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew Jacobs (JIRA)" <>
Subject [jira] [Created] (IMPALA-5651) Investigate cheaper stack trace printing mechanism
Date Wed, 12 Jul 2017 15:35:00 GMT
Matthew Jacobs created IMPALA-5651:

             Summary: Investigate cheaper stack trace printing mechanism
                 Key: IMPALA-5651
             Project: IMPALA
          Issue Type: Improvement
          Components: Backend
    Affects Versions: Impala 2.9.0
            Reporter: Matthew Jacobs

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.

This message was sent by Atlassian JIRA

View raw message