Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here. Want to know more about what has changed? Check out the Community News blog.

Impala Admission control maximum concurrency queries: global or per impalad?

SOLVED Go to solution

Impala Admission control maximum concurrency queries: global or per impalad?

Explorer

Hi,

 

If I set the following property in Impala config for admission control and pool "default", in llama-site.xml:

 

<property>
   <name>llama.am.throttling.maximum.placed.reservations.root.default</name>
   <value>4</value>
</property>

 

Suppose I have 3 Impala nodes and all of them have the same configuration above.

Does that mean I can run up to 12 concurrent queries (4 in each impalad) in default pool or just 4 overall?

 

Thanks,

Paulo.

 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Impala Admission control maximum concurrency queries: global or per impalad?

Cloudera Employee

the property "llama.am.throttling.maximum.placed.reservations.root.*" places a limit on the total number of queries across the cluster. So in this case you can only run 4 overall

2 REPLIES 2

Re: Impala Admission control maximum concurrency queries: global or per impalad?

Cloudera Employee

the property "llama.am.throttling.maximum.placed.reservations.root.*" places a limit on the total number of queries across the cluster. So in this case you can only run 4 overall

Re: Impala Admission control maximum concurrency queries: global or per impalad?

Explorer
Thanks a lot!