[jira] [Commented] (IMPALA-10749) Add Runtime Filter Publish info to Node Lifecycle Event Timeline

["Quanlong Huang (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-10749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504770#comment-17504770 ] 

Quanlong Huang commented on IMPALA-10749:
-----------------------------------------

+1 on this in case the filters arrive late due to other issues (e.g. network).

BTW, the arrival time in the "Per Node Profiles" section mentioned by [~rizaon] above is something like these:
{code:java}
    Per Node Profiles:
      ...
      quanlong-OptiPlex-BJ:27000:
        Filter 1 arrival: 262ms
        Filter 0 arrival: 263ms
      ...
      quanlong-OptiPlex-BJ:27001:
        Filter 1 arrival: 262ms
        Filter 0 arrival: 263ms
{code}

> Add Runtime Filter Publish info to Node Lifecycle Event Timeline
> ----------------------------------------------------------------
>
>                 Key: IMPALA-10749
>                 URL: https://issues.apache.org/jira/browse/IMPALA-10749
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Zoltán Borók-Nagy
>            Priority: Major
>
> Currently we only have the following info about runtime filters at the HASH JOIN NODE in the profile:
> {noformat}
> Runtime filters: 1 of 1 Runtime Filter Published
> {noformat}
> But it would be useful to know when the runtime filters were published. We could add this information to the Node Lifecycle Event Timeline.
> E.g. in test failures like IMPALA-10747 it would be good to know when the runtime filters were published.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

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