Impala tuning

[#1]

Hello Team,

can you please advise how I can proceed to:

1. Limit the total # of concurrently executing Impala queries system wide
2. Limit the memory that an Impala query can use before swapping
3. Protect Impala from Yarn contention with Static Service Pools
4. Implement Admission Control Queues for different Impala User Groups
─ Limit concurrent queries for each queue/pool
─ Implement memory limits on the queue/pools and Running Queries
5. Put a disk limit on runaway queries specifying the maximum amount of disk
storage, in bytes, that any Impala query can consume on any host

on Cloudera?

Thanks,

Roshan

[#2 · Accepted solution]

Hi Roshan,

This is a good starting guide on Impala admission control management. Please review it first and see if you still have questions after.

https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/impala-manage/topics/impala-admission.html

Kind regards,

Alex

[#3]

Hi Alex,

thanks for sharing.

I will review it.

Regards,

Roshan

[#4]

@roshanbi, have you resolved 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.