[
https://issues.apache.org/jira/browse/IMPALA-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-9772:
----------------------------------
Component/s: Docs
> mem_limit docs are stale
> ------------------------
>
> Key: IMPALA-9772
> URL: https://issues.apache.org/jira/browse/IMPALA-9772
> Project: IMPALA
> Issue Type: Documentation
> Components: Docs
> Reporter: Tim Armstrong
> Assignee: shajini thayasingh
> Priority: Major
>
> https://impala.apache.org/docs/build/html/topics/impala_mem_limit.html has
> some discussion about "cancelling queries" that is out of date
> > If query processing exceeds the specified memory limit on any node, either
> > the per-query limit or the impalad limit, Impala cancels the query
> > automatically. Memory limits are checked periodically during query
> > processing, so the actual memory in use might briefly exceed the limit
> > without the query being cancelled.
> This has been out-of-date for a long time. We already have a discussion of
> what actually happens in the spill-to-disk section here -
> https://impala.apache.org/docs/build/html/topics/impala_scalability.html. I
> think all of the information in this paragraph is now inaccurate.
> "Usage notes" should probably refer to the admission control docs, which
> discusses how to configure memory resource management in detail -
> https://impala.apache.org/docs/build3x/html/topics/impala_admission.html
> The last bit of the example with the error is also very out of date - that
> query will either succeed reliably or be rejected by admission control
> because the memory limit is set too low.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
