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 2025/01/07 05:09:00 UTC

[jira] [Resolved] (IMPALA-13643) HDFS_SCANNER_THREAD_CHECK_SOFT_MEM_LIMIT is ineffective in MT_DOP > 0

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

Riza Suminto resolved IMPALA-13643.
-----------------------------------
    Fix Version/s: Impala 4.5.0
       Resolution: Fixed

> HDFS_SCANNER_THREAD_CHECK_SOFT_MEM_LIMIT is ineffective in MT_DOP > 0
> ---------------------------------------------------------------------
>
>                 Key: IMPALA-13643
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13643
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Test
>            Reporter: Riza Suminto
>            Assignee: Riza Suminto
>            Priority: Minor
>             Fix For: Impala 4.5.0
>
>
> Debug action HDFS_SCANNER_THREAD_CHECK_SOFT_MEM_LIMIT exist inside HdfsScanNode (hdfs-scan-node.cc) code path. MT_DOP > 0 executes using HdfsScanNodeMt (hdfs-scan-node-mt.cc) rather than HdfsScanNode, and always start single scanner thread per ScanNode.  Thus, no need to exercise HDFS_SCANNER_THREAD_CHECK_SOFT_MEM_LIMIT and MT_DOP > 0 combination.
> [https://github.com/apache/impala/blob/99529db6ad62ddc34cbfd924d7e41b1fce5b60a2/tests/query_test/test_scanners.py#L70] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)