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 "Balazs Jeszenszky (Jira)" <ji...@apache.org> on 2021/10/14 11:33:00 UTC

[jira] [Assigned] (IMPALA-6756) Order children of profiles in a canonical way

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

Balazs Jeszenszky reassigned IMPALA-6756:
-----------------------------------------

    Assignee:     (was: Balazs Jeszenszky)

> Order children of profiles in a canonical way
> ---------------------------------------------
>
>                 Key: IMPALA-6756
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6756
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>    Affects Versions: Impala 2.12.0
>            Reporter: Lars Volker
>            Priority: Trivial
>              Labels: supportability
>
> IMPALA-6694 addressed an issue where variations in the execution order across multiple backends changed the order of a fragment instance's profile children. Instead of relying on the order in which children are created on the worker nodes and reported to the coordinator, we should introduce a canonical order, e.g. have the non-exec-node children appear before the exec-nodes, and order them alphabetically. [This discussion in the review|https://gerrit.cloudera.org/#/c/9749/3/be/src/util/runtime-profile.cc@358] has some more details.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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