[ https://issues.apache.org/jira/browse/IMPALA-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pooja Nilangekar updated IMPALA-6153: ------------------------------------- Comment: was deleted (was: I ) > 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: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org