[
https://issues.apache.org/jira/browse/IMPALA-10590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Tauber-Marshall resolved IMPALA-10590.
---------------------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Ensure admissiond stays in sync with coordinators
> -------------------------------------------------
>
> Key: IMPALA-10590
> URL: https://issues.apache.org/jira/browse/IMPALA-10590
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Affects Versions: Impala 4.0
> Reporter: Thomas Tauber-Marshall
> Assignee: Thomas Tauber-Marshall
> Priority: Major
> Fix For: Impala 4.0
>
>
> Currently, its possible for the admission service to have an incorrect view
> of what resources are being used in the cluster if there are rpc failures.
> For example, if the ReleaseQuery rpc fails, the coordinator will retry a few
> times and then give up. In this case, a query has completed by the admission
> service doesn't know and will not allow other queries to be scheduled with
> those resources.
> We can solve this by adding a periodic heartbeat rpc from coordinators to the
> admission service. This heartbeat will include the query ids for all queries
> currently running at each coordinator, and then the admission service can
> clean up resources allocated to any queries that are not in the list, on the
> assumption that those queries must have completed already.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
