https://community.cloudera.com/t5/Support-Questions/Tez-vertex-failed-due-to-it-s-own-failure-DAG-did-not/m-p/219562#M181450 <P><EM>@<A href="https://community.hortonworks.com/users/43176/dayakarjd.html">D G</A></EM></P><P><EM>Would you be able to find the task attempt that actually failed. That task attempt can show you which machine and YARN container is ran on. Sometimes the logs dont have the error because it logged into stderr. In that case, the stderr from the containers YARN logs may show the error. <BR /></EM></P><P><EM>Could you set this variable and re-run the query </EM></P><PRE>set hive.execution.engine=tez; set hive.auto.convert.join=true; set hive.auto.convert.join.noconditionaltask=true; set hive.auto.convert.join.noconditionaltask.size=405306368; set hive.vectorized.execution.enabled=true; set hive.vectorized.execution.reduce.enabled =true; set hive.cbo.enable=true; set hive.compute.query.using.stats=true; set hive.stats.fetch.column.stats=true; set hive.stats.fetch.partition.stats=true; set hive.merge.mapfiles =true; set hive.merge.mapredfiles=true; set hive.merge.size.per.task=134217728; set hive.merge.smallfiles.avgsize=44739242; set mapreduce.job.reduce.slowstart.completedmaps=0.8</PRE><P><EM>Please let me know if that helped</EM></P> Fri, 13 Oct 2017 04:46:36 GMT Shelton 2017-10-13T04:46:36Z