[
https://issues.apache.org/jira/browse/IMPALA-14881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-14881.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Scanner threads can have incorrect instance id with mt_dop=0
> ------------------------------------------------------------
>
> Key: IMPALA-14881
> URL: https://issues.apache.org/jira/browse/IMPALA-14881
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Csaba Ringhofer
> Assignee: Csaba Ringhofer
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> IMPALA-6416 added automatic setting of instance id based on parent thread,
> but for scanner threads the parent thread can belong to an unrelated thread
> that releases a thread token.
> The problematic change:
> https://gerrit.cloudera.org/#/c/9053/9/be/src/exec/hdfs-scan-node.cc
> ThreadTokenAvailableCb can be called from outside the instance through as it
> is registered in ThreadResourcePool::AddThreadAvailableCb
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
