Created 09-23-2025 05:40 AM
Hello everyone,
Is it possible to limit the memory for executing queries for an LDAP group in CDP 7.1.7? This would allow creating a memory pool for each group so that if a user in that group launches a memory-intensive query, it does not impact other users in the cluster.
BR!
Created 09-24-2025 01:43 PM
I think you would need to set up the Submission Access Control per pool, as mentioned here: https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/impala-manage/topics/impala-dynamic-pool-conf...
This is in addition to the memory-based admission control per pool as explained here: https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/impala-manage/topics/impala-admission.html and other links under https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/impala-manage/topics/impala-resource-manageme....
As the result you should get Impala memory 'divided' (virtually, not physically!) between the pools, and each pool accessible only by the groups as configured.
Created 09-24-2025 01:43 PM
I think you would need to set up the Submission Access Control per pool, as mentioned here: https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/impala-manage/topics/impala-dynamic-pool-conf...
This is in addition to the memory-based admission control per pool as explained here: https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/impala-manage/topics/impala-admission.html and other links under https://docs.cloudera.com/cdp-private-cloud-base/7.1.7/impala-manage/topics/impala-resource-manageme....
As the result you should get Impala memory 'divided' (virtually, not physically!) between the pools, and each pool accessible only by the groups as configured.
Created 09-30-2025 04:18 AM
Hello @Boris G,
Thanks for this response. It works for me.
Created 09-29-2025 01:18 PM
@Hambaliou14 Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
Regards,
Diana Torres,