You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Siddharth Seth (JIRA)" <ji...@apache.org> on 2013/10/05 07:50:41 UTC

[jira] [Created] (TEZ-530) YARNTezDAGChild still not exiting correctly

Siddharth Seth created TEZ-530:
----------------------------------

             Summary: YARNTezDAGChild still not exiting correctly
                 Key: TEZ-530
                 URL: https://issues.apache.org/jira/browse/TEZ-530
             Project: Apache Tez
          Issue Type: Bug
            Reporter: Siddharth Seth


Hung thread from the trace.
{code}
"main" prio=5 tid=7fb4af000000 nid=0x10c35f000 waiting on condition [10c35d000]
   java.lang.Thread.State: WAITING (parking)
  at sun.misc.Unsafe.park(Native Method)
  - parking to wait for  <7fd3138f0> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
  at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
  at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987)
  at org.apache.tez.mapreduce.input.MRInput.getReader(MRInput.java:207)
  at org.apache.tez.mapreduce.processor.map.MapProcessor$NewRecordReader.<init>(MapProcessor.java:213)
  at org.apache.tez.mapreduce.processor.map.MapProcessor$NewRecordReader.<init>(MapProcessor.java:206)
  at org.apache.tez.mapreduce.processor.map.MapProcessor.runNewMapper(MapProcessor.java:180)
  at org.apache.tez.mapreduce.processor.map.MapProcessor.run(MapProcessor.java:124)
  at org.apache.tez.runtime.LogicalIOProcessorRuntimeTask.run(LogicalIOProcessorRuntimeTask.java:149)
  at org.apache.hadoop.mapred.YarnTezDagChild$4.run(YarnTezDagChild.java:430)
  at java.security.AccessController.doPrivileged(Native Method)
  at javax.security.auth.Subject.doAs(Subject.java:396)
  at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1499)
  at org.apache.hadoop.mapred.YarnTezDagChild.main(YarnTezDagChild.java:420)
{code}

That's the 3rd jira for the same issue. I think we need to consider running a Runtime.halt, after attempting a System.exit.



--
This message was sent by Atlassian JIRA
(v6.1#6144)