[
https://issues.apache.org/jira/browse/IMPALA-10583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riza Suminto resolved IMPALA-10583.
-----------------------------------
Fix Version/s: Impala 4.0
Resolution: Fixed
> Result spooling hang with unbounded spooling mem limit.
> -------------------------------------------------------
>
> Key: IMPALA-10583
> URL: https://issues.apache.org/jira/browse/IMPALA-10583
> Project: IMPALA
> Issue Type: Bug
> Components: Backend, Frontend
> Affects Versions: Impala 4.0
> Reporter: Riza Suminto
> Assignee: Riza Suminto
> Priority: Major
> Fix For: Impala 4.0
>
>
> Looking at BufferedPlanRootSink and SpillableRowBatchQueue, it seems the code
> fail to anticipate if max_spilled_result_spooling_mem = 0 (unbounded).
> max_unpinned_bytes_ will be set to 0 and SpillableRowBatchQueue::IsFull()
> will always be true. We should change max_unpinned_bytes_ to INT64_MAX if
> max_spilled_result_spooling_mem = 0.
> Another bug happen when setting max_result_spooling_mem = 0 (unbounded). When
> this happen, PlanRootSink.java will peg maxMemReservationBytes to always
> equal to minMemReservationBytes. I think we should override it to the default
> max_result_spooling_mem (100MB) or set it equal to mem_limit of the query
> pool.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
