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 "Michael Smith (Jira)" <ji...@apache.org> on 2023/12/21 18:30:00 UTC
[jira] [Commented] (IMPALA-12660) TSAN error in ImpalaServer::QueryStateRecord::Init
[ https://issues.apache.org/jira/browse/IMPALA-12660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799537#comment-17799537 ]
Michael Smith commented on IMPALA-12660:
----------------------------------------
This happens in the new {{internal-server-test}} [~jasonmfehr].
What appears to happen is that the test makes a request to {{/queries}}, which construct a {{QueryStateRecord}} from a {{ClientRequestState}}. While reading from {{TExecRequest}} (which {{ClientRequestState}} holds a pointer to), {{RunFrontendPlanner}} calls {{GetExecRequest}} to fill the same {{TExecRequest}} from the frontend.
That suggests to me that the query is being registered early for some reason, or a previously unidentified race in updating {{QueryDriver::exec_request_}}'s state. Looking further up the stack, this happens in {{ImpalaServer::ExecuteInternal}}, which first calls {{RegisterQuery}} (making it visible to {{QueryStateHandler}}), then {{RunFrontendPlanner}}. So this looks like a latent race that {{internal-server-test}} exposed.
> TSAN error in ImpalaServer::QueryStateRecord::Init
> --------------------------------------------------
>
> Key: IMPALA-12660
> URL: https://issues.apache.org/jira/browse/IMPALA-12660
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Csaba Ringhofer
> Assignee: Michael Smith
> Priority: Critical
> Attachments: tsan.txt
>
>
> See error in tsan.txt
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org