thanks for your reply @ngarg  I am not sure if you got my point.  LLAP is showing that it is consuming 99% of the resources in the queue (own queue)  And if this is the case there is not enough memory for AM - at least this is my assumption.   So my question is - if this is desired to see that LLAP app is showing so high usage of its own queue just by running LLAP app/daemon?  with below(table "not working LLAP") all queries are in the accepted state waiting for resources. Once we changed  Memory per Daemon  to use more/less 3gb memory less than suggested by Ambari, LLAP started to give us results    Both tables below are showing LLAP while no running queries    Not working LLAP  Used Capacity:Configured Capacity:Configured Max Capacity:Absolute Used Capacity:Absolute Configured Capacity:Absolute Configured Max Capacity:Used Resources:Configured Max Application Master Limit:Max Application Master Resources:Used Application Master Resources:Max Application Master Resources Per User: 99.3% 100.0% 100.0% 99.3% 100.0% 100.0% <memory:232448, vCores:10> 100.0 <memory:294912, vCores:36> <memory:17408, vCores:5> <memory:294912, vCores:36>     Working LLAP  Used Capacity:Configured Capacity:Configured Max Capacity:Absolute Used Capacity:Absolute Configured Capacity:Absolute Configured Max Capacity:Used Resources:Configured Max Application Master Limit:Max Application Master Resources:Used Application Master Resources:Max Application Master Resources Per User: 78.8% 100.0% 100.0% 78.8% 100.0% 100.0% <memory:232448, vCores:10> 100.0 <memory:294912, vCores:36> <memory:17408, vCores:5> <memory:294912, vCores:36> ... View more