here are two orphaned TezChilds

https://www.dropbox.com/s/7ys2oopznhbcu3t/tezchild.threads.txt?dl=0
https://www.dropbox.com/s/qpkknk21wo2k8qb/tezchild2.threads.txt?dl=0

jps -m | grep TezChild
74763 TezChild 192.168.1.29 65336 container_1409846253566_0004_01_000002 
application_1409846253566_0004 1
78633 TezChild 192.168.1.29 63480 container_1409854562430_0003_01_000002 
application_1409854562430_0003 1

my code is calling

"TezChild" daemon prio=5 tid=0x00007fafb3472800 nid=0x2b07 waiting on condition 
[0x000000010be8e000]
   java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x00000007ee265f78> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
        at 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
        at 
org.apache.tez.mapreduce.input.MRInputLegacy.checkAndAwaitRecordReaderInitialization(MRInputLegacy.java:135)
        at 
org.apache.tez.mapreduce.input.MRInputLegacy.init(MRInputLegacy.java:109)

if the issue isn't obvious on your side, i'll try and figure out what DAG is 
responsible (i'm running lots of random tests, and just found two of these 
floating around).


On Sep 3, 2014, at 8:44 PM, Chris K Wensel <[email protected]> wrote:

> 
> this is confirmed on 0.5.0 (from apache release mvn repo)
> 
> just caused a hang by running a single test, the TezChild did linger, but 
> exited
> 
> https://www.dropbox.com/s/86ryr1ka93xaiph/dagapp.threads.txt?dl=0
> 
> ckw
> 
> On Sep 3, 2014, at 8:26 PM, Siddharth Seth <[email protected]> wrote:
> 
>> Chris,
>> Are you on the latest version of Tez (ideally the 0.5 release, which just 
>> went out today). There was an issue with hanging DAGAppMasters, which was 
>> resolved recently.
>> Otherwise, could you please include stack traces for the hung processes.
>> 
>> Thanks
>> - Sid
>> 
>> 
>> On Wed, Sep 3, 2014 at 8:05 PM, Chris K Wensel <[email protected]> wrote:
>> 
>> I'm finding after running MiniTezCluster I find a few DAGApp and possibly a 
>> TezChild process hanging around after calling jps.
>> 
>> This is problematic with our CI servers (they start to add up) let a alone 
>> my dinky laptop.
>> 
>> Is there a TezConfiguration setting I'm likely missing to prevent these.
>> 
>> ckw
>> 
>> --
>> Chris K Wensel
>> [email protected]
>> http://concurrentinc.com
>> 
>> 
> 
> --
> Chris K Wensel
> [email protected]
> http://concurrentinc.com
> 

--
Chris K Wensel
[email protected]
http://concurrentinc.com

Reply via email to