[
https://issues.apache.org/jira/browse/IMPALA-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zsombor Fedor updated IMPALA-8602:
----------------------------------
Description:
When resource limits apply to a group of users via {{fair-scheduler.xml}} and
{{llama-site.xml}}, if the users have no access to these files or the UIs where
you can manage these, they have no way to tell what limits apply to them.
With the limits set locally, (ex.: {{SET MEM_LIMIT=1073741824;}}), one can tell
the resource limits applied via the {{SET;}} query. But when Admission Control
manages these limits, the output of the {{SET;}} statement is not helpful,
because for a query the planner itself picking the {{fair-scheduler.xml}} and
{{llama-site.xml}} files up.
There is also a misleading sentence in the DOCS regarding this issue:
{quote}The {{SET}} statement specifies values for query options that control
the runtime behavior of other statements within the same session.[1]
{quote}
This sentence clearly does not apply when Admission Control enabled, explained
above.
A new statement/function would be great, whereby the users could examine the
resource limits apply to them from the client side.
[1]: [https://impala.apache.org/docs/build/html/topics/impala_set.html]
was:
When resource limits apply to a group of users via {{fair-scheduler.xml}} and
{{llama-site.xml}}, if the users have no access to these files or the UIs where
you can manage these, they have no way to tell what limits apply to them.
With the limits set locally, (ex.: {{SET MEM_LIMIT=1073741824;}}), one can tell
the resource limits applied via the {{SET;}} query. But when Admission Control
manages these limits, the output of the {{SET;}} statement is not helpful,
because for a query the planner itself picking the {{fair-scheduler.xml}} and
{{llama-site.xml}} files up.
There is also a misleading sentence in the DOCS regarding this issue:
{quote}The {{SET}} statement specifies values for query options that control
the runtime behavior of other statements within the same session.
{quote}
This sentence clearly does not apply when Admission Control enabled, explained
above.
A new statement/function would be great, whereby the users could examine the
resource limits apply to them from the client side.
> Client level transparency of Admission Control resource limits
> --------------------------------------------------------------
>
> Key: IMPALA-8602
> URL: https://issues.apache.org/jira/browse/IMPALA-8602
> Project: IMPALA
> Issue Type: New Feature
> Components: Clients
> Reporter: Zsombor Fedor
> Priority: Minor
>
> When resource limits apply to a group of users via {{fair-scheduler.xml}} and
> {{llama-site.xml}}, if the users have no access to these files or the UIs
> where you can manage these, they have no way to tell what limits apply to
> them.
> With the limits set locally, (ex.: {{SET MEM_LIMIT=1073741824;}}), one can
> tell the resource limits applied via the {{SET;}} query. But when Admission
> Control manages these limits, the output of the {{SET;}} statement is not
> helpful, because for a query the planner itself picking the
> {{fair-scheduler.xml}} and {{llama-site.xml}} files up.
> There is also a misleading sentence in the DOCS regarding this issue:
> {quote}The {{SET}} statement specifies values for query options that control
> the runtime behavior of other statements within the same session.[1]
> {quote}
> This sentence clearly does not apply when Admission Control enabled,
> explained above.
> A new statement/function would be great, whereby the users could examine the
> resource limits apply to them from the client side.
> [1]: [https://impala.apache.org/docs/build/html/topics/impala_set.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
