[
https://issues.apache.org/jira/browse/IMPALA-8602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851995#comment-16851995
]
Tim Armstrong commented on IMPALA-8602:
---------------------------------------
You can see the effective query options in the query profile. It would be
helpful to know if there's something that's *not* in the query profile that
would be useful to know. E.g. a resource limit or some information about how a
policy was applied.
It's not possible to tell exactly what policies will apply to a user, since the
model is that each query is mapped to a pool separately. E.g. REQUEST_POOL can
be set to different values for different queries, or in future we might map
queries to different pools based on arbitrary policies.
I can see some value in providing a way to expose policies but I'm not sure how
it could be presented in a user-friendly way that would be useful for figuring
out what policies apply. Would also need some thought about whether anything in
the policies should be considered sensitive.
> 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]
