Hi Rajesh We have this set in tez-site.xml and also before running the JDBC sql query we first fire a sql setting this parameter too.
Thanks and Regards Prabakaran.N aka NP nsn, Bangalore When "I" is replaced by "We" - even Illness becomes "Wellness" From: ext Rajesh Balamohan [mailto:[email protected]] Sent: Tuesday, May 20, 2014 12:58 PM To: [email protected] Cc: Sachwani, Yogesh (NSN - IN/Bangalore) Subject: Re: Tez - Hive Parallel queries Hi Prbakaran, Are you passing these parameters via CLI or via tez-site.xml? ~Rajesh.B On Tue, May 20, 2014 at 12:29 PM, Natarajan, Prabakaran 1. (NSN - IN/Bangalore) <[email protected]<mailto:[email protected]>> wrote: Hi, We tried running tez queries on Hive server 1 with 10 threads in Parallel. First 10 queries go through fine and result comes in 16-18 seconds but when we fire the same queries again on same connection we find that connection/queries are blocked for more than 200 seconds and only after some 200-260 seconds the queries get fired. In YARN job tracker UI we see the previous query containers still not being closed and once they are closed after > 200 seconds the new queries get fired . We tried both enabling tez AM reuse( same JVM size for map and reduce ) and 100 ms value for "tez.am.container.session.delay-allocation-millis" parameter but none of these help. Any idea on how can we reduce this > 200 sec block/latency Thanks and Regards Prabakaran.N aka NP nsn, Bangalore When "I" is replaced by "We" - even Illness becomes "Wellness" -- ~Rajesh.B
