Setting up LLAP
Using Ambari, you can set up basic, low-latency analytical processing (LLAP) by
accepting the default
llap queue and most, if not all, other default
- You have installed Ambari 2.7.1.
- You added and started YARN, Tez, and dependencies that Ambari prompts you to add.
- You added and started the Hive service.
Optionally, as an advanced LLAP user, familiar with capacity scheduling in YARN, you
can set up a customized query queue rather than using the default
llap queue for LLAP.
Interactive Query displays a range of values for default Maximum Total Concurrent Queries based on the number of nodes that you selected and the number of CPUs in the Hive LLAP cluster. The Ambari wizard typically calculates appropriate values for the following LLAP property settings in Interactive Query, so you can usually accept the defaults:
- Memory per Daemon
- YARN container size for each daemon (MB)
- In-Memory Cache per Daemon
- Size of the cache in each container (MB)
- Number of executors per LLAP Daemon
- The number of fragments that can execute in parallel on a daemon
When you enable Hive LLAP, the Run as end user and Hive user security settings have no effect. These controls affect batch-processing mode.