[
https://issues.apache.org/jira/browse/IMPALA-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Sherman resolved IMPALA-13596.
-------------------------------------
Fix Version/s: Impala 4.5.0
Resolution: Fixed
> Verify Admission Control configuration at startup
> -------------------------------------------------
>
> Key: IMPALA-13596
> URL: https://issues.apache.org/jira/browse/IMPALA-13596
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 4.4.0
> Reporter: Andrew Sherman
> Assignee: Andrew Sherman
> Priority: Major
> Fix For: Impala 4.5.0
>
>
> The Admission Control configuration is split across the two files
> -fair_scheduler_allocation_path=fair-scheduler.xml
> -llama_site_path=llama-site.xml
> We lazily load the configuration for a pool when a query is submitted to that
> pool. This is probably not a good time to fail the server.
> In addition a possibly dangerous configuration for a pool in the XML files
> might never actually be used.
> Add a configuration verification step at server startup. This will log
> warning messages if there is an inconsistency in the configuration.
> There could be multiple checks, for example we could flag if a Root level
> User Quota value is less than a pool level User Quota.
> We could also detect duplicate entries in the configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
