You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Riza Suminto (Jira)" <ji...@apache.org> on 2021/03/12 17:35:00 UTC
[jira] [Created] (IMPALA-10583) Result spooling hang with unbounded
spooling mem limit.
Riza Suminto created IMPALA-10583:
-------------------------------------
Summary: 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
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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org