Member since
11-15-2018
12
Posts
0
Kudos Received
0
Solutions
01-19-2021
06:28 AM
There are no preconfigured queues under the parent queue. That checkbox seems to be tied to placement rules. However, for CDP, the only placement rules that allow autocreation of leafs is tied to "root.users". In CDH, you could have a leaf queue created anywhere if "create queue if non-existent" was checked. In CDP, the freedom to do that seems limited to things under root.users... Hopefully I'm missing something. The inability to create leaf queues under arbitrary parent queues would be a big step backwards in terms of queue flexibilty.
... View more
06-02-2020
07:33 AM
Thanks Ferenc. As mentioned, we cannot use CDP in the foreseeable future, nor are we customizing the CDH release in any real way -- simply adding Livy on a new edge node, which should work and should be relatively straightforward, but in this case is not. Enterprise Support (which we pay for) is telling us to ask the Community for guidance. So, here we are. If anyone has any guidance in terms of actually getting past this local auth mapping issue, we would greatly appreciate it. Best, Mike
... View more
04-24-2019
08:51 AM
Could you advise if there is a solution to the problem, when Impala assigns heavy query parts to busy executors. For example the following was faced at CDH 5.16 with Impala 2.12.0: Impala has several (let's say 5) executors each having ~100GB RAM. Impala admission control is used. The mem_limit is set default (or about default ~80%), e.g. 80GB. The first relatively long and heavy query (let's name it Query1) comes and one of its steps take ~70GB RAM at executor1, i.e. there is ~10GB available RAM at this executor for reservation. Other 4 executor servers are nearly idle. At the same time the second query (let's name Query2) comes, which requires 40GB RAM, and it might happen the Query2 is assigned to the executor1, which is busy. So the Query2 fails due to it cannot allocate/reserve the memory. Is there a way to configure Impala to assign fragments/query parts to less busy executors? So far the concurrency reduction or reservation removal (since reserved memory amount usually is larger than really used) might work, but I see it too inefficient to use only 1-2 executors out of 5. Impala on YARN potentially might help, but as far as I see, it requires Llama, which is deprecated and is going to be removed soon.
... View more