You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2020/03/07 03:44:00 UTC
[jira] [Resolved] (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:all-tabpanel ]
Riza Suminto resolved IMPALA-8674.
----------------------------------
Resolution: Fixed
The fix has been merged.
> 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)