> * i used Gopal's fragment for tez-site.xml >(https://github.com/t3rmin4t0r/tez-autobuild/blob/llap/tez-site.xml.frag)
Please check that the tez.lib.uris is filled out properly. I suspect it's all already setup since the CLI mode works anyway, but cross-check that the HS2 classpath does have a tez-site.xml in it. > * nothing gets submitted to yarn. I have a dumb question, which I didn't think about when you asked this in the Tez list - Is date_key a partition column? You can try turning off optimizations from my list, which can cause some dumb stuff (particularly with S3/Azure). set hive.optimize.null.scan=false; set hive.optimize.metadataonly=false; set hive.fetch.task.conversion=none; And assuming your goal is to run this as fast as possible (reads the count/min/max fast per partition). set hive.compute.query.using.stats=true; > and that's it. this is where it stalls out. nothing more in hive.log; >nothing more on the client. so its kinda strange. ... > wondering what further steps i can take to trace down the problem. Any >ideas? Log lines with TezSession* would the ones to look into, even at INFO log levels. The log level doesn't seem to have lowered FWIW, so a jstack definitely helps. I have noticed issues with some YARN setups (Pivotal installs for instance), which are configured to do strict queues (and occasionally to reject such logins). At least for capacity scheduler, I know the config looks like yarn.scheduler.capacity.root.default.state=STOPPED to prevent anyone from starting any jobs in "default" queue. Cheers, Gopal
