[
https://issues.apache.org/jira/browse/IMPALA-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072252#comment-18072252
]
ASF subversion and git services commented on IMPALA-6416:
---------------------------------------------------------
Commit 764e225292e07a8de11ed924dbdde4c9221b5ff8 in impala's branch
refs/heads/master from Csaba Ringhofer
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=764e22529 ]
IMPALA-14881: Fix instance id in scanner threads
Since IMPALA-6416 the instance id of new threads is inherited
from parent thread instead of setting explicitly. This is not
correct in case of scanner threads (mt_dop=0) when
HdfsScanNode::ThreadTokenAvailableCb is called through
ThreadResourcePool's callback where the thread can come from
an unrelated query.
Note that this issue only affects diagnostics.
Testing:
- tested manually by running parallel scan heavy queries and adding
logging for fragment id in scanner thread - before the fix these
log lines could contain two different instance ids
Change-Id: I2ccfb94353843eaa83cf7371788d0fc151fd3e50
Reviewed-on: http://gerrit.cloudera.org:8080/24174
Reviewed-by: Zoltan Borok-Nagy <[email protected]>
Reviewed-by: Michael Smith <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Extend Thread::Create to track fragment instance id automatically based on
> parent's fid
> ---------------------------------------------------------------------------------------
>
> Key: IMPALA-6416
> URL: https://issues.apache.org/jira/browse/IMPALA-6416
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Zoltán Borók-Nagy
> Assignee: Zoltán Borók-Nagy
> Priority: Major
> Fix For: Impala 2.12.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
