> Looking at the doc i thought this config setting would influence those Tez > jobs from hanging around (tez.session.am.dag.submit.timeout.secs) but testing > proved otherwise. It didn't seem to have any affect. > So i ask. How to force off those Tez jobs organically? Or is there perhaps > something else i'm missing?
A jstack of the Tez AM would be useful. My guess is that this is related to ATS. tez.yarn.ats.event.flush.timeout.millis=-1L; Is the default and if ATS is down for whatever reason, Tez queries will wait infinite time to flush all events to ATS. You can probably set that to 600000L and see if the AMs disappear after 10 minutes. Before TEZ-1701, this was set to 3 seconds which broke the UI when the ATS instance was temporarily unavaible. Cheers, Gopal
