Uploaded image for project: 'Apache Tez'
  1. Apache Tez
  2. TEZ-496 Pending sub-tasks of TEZ-398
  3. TEZ-493

Task JVMs hanging around even after the AM/app has completed

    XMLWordPrintableJSON

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.2.0
    • Component/s: None
    • Labels:
      None

      Description

      "TezTaskEventRouter[attempt_1380003134543_0003_1_00_000000_1]" prio=5 tid=7ff149477800 nid=0x10ef34000 waiting on condition [10ef33000]
         java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <7f00c9148> (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 java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:399)
        at org.apache.tez.engine.newruntime.LogicalIOProcessorRuntimeTask$1.run(LogicalIOProcessorRuntimeTask.java:407)
        at java.lang.Thread.run(Thread.java:680)
      

      That's one trace, from a process started on 09/23. Don't think any fixes went in after that, which would resolve this.

      Saw additional stuck processes because the Inputs/Ouputs created non-daemon threads (which also happened to be blocking on a queue)

        Attachments

        1. TEZ-493.1.patch
          3 kB
          Hitesh Shah

          Activity

            People

            • Assignee:
              hitesh Hitesh Shah
              Reporter:
              sseth Siddharth Seth
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: