@ccasano I'd also like to add to my comment that default LLAP leverages the LRFU algorithm with a pre-emption strategy on the Frequently Used side. This means that LLAP will always preempt long running queries in favor of short, adhoc queries yet it still will allow for the occasional "bring-back-all-the-data" scenario without flushing adhoc query cache. This allows for better query concurrency and provides optimal performance for the majority of BI workloads. In addition, LLAP does not use YARN containers which would limit concurrency since each container is a user session, aka job. Most BI use cases involve many users running ad hoc queries and then keeping their session open as they look at the reports. By leverages TEZ AM for queries LLAP gets much higher concurrency. The combination of LLAP's LRFU algorithm, use of TEZ AM, caching, and AtScale's Adaptive Cache, users get a nice boost in performance and concurrency out-of-the-box. ... View more

https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.QueryDatabaseTable/ ... View more

Hi @James Dinkel I'm guessing there is a memory sizing issue. Make sure you follow these sizing rules: MemPerDaemon (Container Size) > LLAP Heapsize (Java process heap) + CacheSize (off heap) +headroom Multiple of yarn min allocation Should be less than yarn.nodemanager.resource.memory-mb Headroom is capped at 6GB QueueSize (Yarn Queue) >= MemPerDaemon * num daemons + slider + (tez AM size * concurrency) Cachesize = MemPerDaemon - (hive tez container * num of executors) Num executors per daemon = (MemPerDaemon - cache_size)/hive tez container size In addition, be sure your LLAP queue is setup appropriately and has sufficient capacity: <queue>.user_limit_factor =1 <queue>.ama-resource-percent =1 (its actually a factor between 0 and 1) <queue>.capacity=100 <queue>.max-capacity=100 ... View more

Hi @suresh krish It appears you may have a Ranger policy preventing access to the table. You can disable Ranger authentication through Ambari in the Hive configs or review the Hive Ranger policies and provide the appropriate authorization. This HCC thread has some additional information https://community.hortonworks.com/questions/64345/how-to-add-another-hiveserver-for-current-metastor.html ... View more

@Yasir Faiz I believe LLAP will be GA in 2.6 which is due out sometime in Q2. The advantage of HDP 2.5 would be to test LLAP and Hive 2.0. Also, HDP 2.5 also includes a number fixes to Hive 1.2.1 1.2.1 http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.5.3/bk_release-notes/content/fixed_issues.html ... View more