Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

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

avatar
Contributor

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

avatar
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

View solution in original post

2 REPLIES 2

avatar
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

avatar
Contributor
Thanks a lot!