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 "Riza Suminto (Jira)" <ji...@apache.org> on 2020/02/26 22:21:00 UTC

[jira] [Commented] (IMPALA-8674) REMOTE runtime filters are always shown as disabled in the final filter routing table

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

Riza Suminto commented on IMPALA-8674:
--------------------------------------

Hi, I'd like to try solve this jira.

My initial thought is to add flag all_publish_complete in Coordinator::FilterState class and set it to true after the last filter publish at Coordinator::BackendState::PublishFilterCompleteCb().

Later in Coordinator::FilterDebugString(), we will check this flag to distinguish between filter that failed and logically disabled vs filter that actually successfully published.

> REMOTE runtime filters are always shown as disabled in the final filter routing table
> -------------------------------------------------------------------------------------
>
>                 Key: IMPALA-8674
>                 URL: https://issues.apache.org/jira/browse/IMPALA-8674
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 3.2.0
>            Reporter: Tim Armstrong
>            Assignee: Riza Suminto
>            Priority: Major
>              Labels: observability, ramp-up
>
> {noformat}
> Final filter table:
> ID  Src. Node  Tgt. Node(s)     Target type  Partition filter  Pending (Expected)  First arrived  Completed   Enabled
> ----------------------------------------------------------------------------------------------------------------------
>  1          6          0, 1  REMOTE, REMOTE      false, false              0 (93)       50s381ms   53s566ms     false
>  0          6             0          REMOTE              true              0 (93)       50s177ms   52s336ms     false
> {noformat}
> The issue is that the filter is disabled after the remote filter is sent out https://github.com/apache/impala/blob/95a1da2/be/src/runtime/coordinator.cc#L987. The code seems to really conflate releasing of resources with filters that were logically disabled.



--
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