[
https://issues.apache.org/jira/browse/IMPALA-2060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-2060.
-----------------------------------
Resolution: Won't Fix
Relates to LLAMA support, which has been removed
> Query resource reservation shouldn't be released until fragments complete
> -------------------------------------------------------------------------
>
> Key: IMPALA-2060
> URL: https://issues.apache.org/jira/browse/IMPALA-2060
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 2.2
> Reporter: Anubhav Dhoot
> Assignee: Matthew Jacobs
> Priority: Minor
> Labels: llama, query-lifecycle, resource-management
> Attachments: impala-llama-unknownreservation.log
>
>
> As seen in the attached log snippet of impala and llama there are cases where
> the query is cancelled so impala releases resources yet later still calls
> into expand CPU resources for llama. Hence we end up returning
> UNKNOWN_RESERVATION_FOR_EXPANSION and an error is printed in the logs. We
> don't think this is causing any real problems because the query is already
> being torn down.
> This only happens when a query is cancelled (internally or externally, e.g.
> if an error occurs) because the fragments are sent a cancellation request
> asynchronously and then immediately after the coordinator shuts down the
> query, including releasing the reservation. The coordinator should wait for
> fragments to finish closing before releasing the reservation.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
