You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Csaba Ringhofer (Jira)" <ji...@apache.org> on 2023/02/07 11:15:00 UTC

[jira] [Updated] (IMPALA-5651) Investigate cheaper stack trace printing mechanism

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

Csaba Ringhofer updated IMPALA-5651:
------------------------------------
    Labels: observability performance  (was: observability perfomance)

> Investigate cheaper stack trace printing mechanism
> --------------------------------------------------
>
>                 Key: IMPALA-5651
>                 URL: https://issues.apache.org/jira/browse/IMPALA-5651
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.9.0
>            Reporter: Matthew Jacobs
>            Priority: Major
>              Labels: observability, performance
>
> 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
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org