[ 
https://issues.apache.org/jira/browse/IMPALA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575432#comment-16575432
 ] 

ASF subversion and git services commented on IMPALA-6153:
---------------------------------------------------------

Commit 2ced56c00b73ecdc92f1021f5d0129a41553e4f2 in impala's branch 
refs/heads/master from poojanilangekar
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=2ced56c ]

IMPALA-6153: Execute UpdateFilter() only for executing queries

This change ensures that coordinator::UpdateFilter is executed
only for queries which are in the EXECUTING state. Additionally,
it also guarantees that coordinator::ReleaseExecResources is
executed only when no other thread is executing UpdateFilter.

Testing: Ran all back-end tests.
Additionally, ran the exhaustive tests with DCHECKs which would
be triggered if the ReleaseExecResources() is executed while any
other thread is executing UpdateFilter().

Change-Id: I669db217f86db5ff2802335e7b1ae8027ea7161c
Reviewed-on: http://gerrit.cloudera.org:8080/11005
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>


> Prevent Coordinator::UpdateFilter() running after query exec resources are 
> released
> -----------------------------------------------------------------------------------
>
>                 Key: IMPALA-6153
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6153
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>            Reporter: Sailesh Mukil
>            Assignee: Pooja Nilangekar
>            Priority: Major
>              Labels: query-lifecycle, runtime-filters
>
> Coordinator::UpdateFilter() and CoordinatorBackendState::PublishFilter() run 
> independent of the lifecycle of any fragment instance. This is problematic 
> during query teardown.
> Specifically we should not release resources for a query if any one of those 
> above functions are still running for that query and we also should not not 
> start running the above methods after resources are released for the query. 
> Also, the 'rpc_params' in UpdateFilter() could potentially hold large amounts 
> of untracked memory, so we should track it.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to