[
https://issues.apache.org/jira/browse/IMPALA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16463043#comment-16463043
]
Bikramjeet Vig commented on IMPALA-5662:
----------------------------------------
[~tarmstrong] You are right that just logging the not_admitted_reason gives
enough information.
Also, which message are you referring to that is logged at level 2?
> Log all information relevant to admission control decision making
> -----------------------------------------------------------------
>
> Key: IMPALA-5662
> URL: https://issues.apache.org/jira/browse/IMPALA-5662
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Reporter: Balazs Jeszenszky
> Assignee: Bikramjeet Vig
> Priority: Major
> Labels: admission-control, observability, resource-management,
> supportability
>
> Currently, when making a decision whether to admit a query or not, the log
> has the following format:
> {code:java}
> I0705 14:43:04.031771 7388 admission-controller.cc:442] Stats:
> agg_num_running=1, agg_num_queued=0, agg_mem_reserved=486.74 MB,
> local_host(local_mem_admitted=0, num_admitted_running=0, num_queued=0,
> backend_mem_reserved=56.07 MB)
> {code}
> Since it's also possible to queue queries due to one node not being able to
> reserve the required memory, we should also log the max(backend_mem_reserved)
> across all nodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
