Thanks for your response. I have used Impala's admission control in our impala cluster, though we have not deployed CM, we set fair-scheduler.xml and llama-site.xml and I think it can finish the same goal comparing to using CM.
I find in admission control, what we can do is limit Max Running Queries and Max Memory Usage for every queries. and in some scenario， we have to overselling the max memory, such as every impalad has 128GB and we set up two pools, one is max running=32 and max memory =4GB, and another is max running=16 and max memory = 2GB, when more and more queries running. we have no ideas about whether the cluster have any problems, maybe we can do some tests. what is more, Without Llama, we can not use cgroups achieve isolation between queries(impala run all queries in one process using different threads). I always think this kind of isolation is too softly. do you have some suggestion? Thanks a lot
