yes, here is the screenshot:
query 1 (green) is started and query 2 (yellow) waits until all the jobs of query one are done
I have checked the screenshot. This is not application concurrency. Reducer phases1 is waiting for all the mappers to get finished. DAG is decided by the optimizer.
Are you using MAPREDUCE or Tez as an execution engine?
I suppose to run TEZ, because I found all the configurations for TEZ ...
But I'm bloody new in this ... So, supposedly I 'm irgnorant too.
Thanks for your fast responses!
In my hive-config (Ambari) are plenty of tez-parameters - so I supposed it is TEZ. I did not found a parameter as 'use tez' or 'use mapreduce' ...
hive.convert.join.bucket.mapjoin.tez is False - may for this ?
My queries are running from beeline
I'm searching now the correct information for the framework, where I found yarn and NOT yarn-tez in the mapred-site-xml ...
I'm totally new to this architecture, so I have to try - I did not find a docu apllicable to our installation (hdp 3.0.1 on powerpc) with ambari.
But thanks a lot, at least I understand, that we are NOT using TEZ ...
Unfortunately I'm still stick with the activation of tez under hive.
setting the properties:
adding in my beeline query
set hive.execution.engine=tez; ## in the query (now it is faster!)
still is always running only ONE of the two, still saying Starting task [Stage-1:MAPRED] in parallel