[ 
https://issues.apache.org/jira/browse/TEZ-1661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jeff Zhang updated TEZ-1661:
----------------------------
    Attachment: TEZ-1661-1.patch

> LocalTaskScheduler hangs when shutdown
> --------------------------------------
>
>                 Key: TEZ-1661
>                 URL: https://issues.apache.org/jira/browse/TEZ-1661
>             Project: Apache Tez
>          Issue Type: Bug
>    Affects Versions: 0.5.0
>         Environment: Local Mode
>            Reporter: Oleg Zhurakousky
>            Assignee: Jeff Zhang
>         Attachments: TEZ-1661-1.patch
>
>
> LocalTaskScheduler hangs on 'take' from the 'taskRequestQueue ' when 
> TezClient shuts down (e.g., TezClient.stop).
> Below is jstack output observed when running in Tez local mode:
> {code}
> "Thread-53" prio=5 tid=0x00007fc876d8f800 nid=0xac07 runnable 
> [0x000000011df90000]
>    java.lang.Thread.State: RUNNABLE
>         at java.lang.Throwable.fillInStackTrace(Native Method)
>         at java.lang.Throwable.fillInStackTrace(Throwable.java:783)
>         - locked <0x00000007b6ce60a0> (a java.lang.InterruptedException)
>         at java.lang.Throwable.<init>(Throwable.java:250)
>         at java.lang.Exception.<init>(Exception.java:54)
>         at java.lang.InterruptedException.<init>(InterruptedException.java:57)
>         at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireInterruptibly(AbstractQueuedSynchronizer.java:1219)
>         at 
> java.util.concurrent.locks.ReentrantLock.lockInterruptibly(ReentrantLock.java:340)
>         at 
> java.util.concurrent.PriorityBlockingQueue.take(PriorityBlockingQueue.java:535)
>         at 
> org.apache.tez.dag.app.rm.LocalTaskSchedulerService$AsyncDelegateRequestHandler.processRequest(LocalTaskSchedulerService.java:310)
>         at 
> org.apache.tez.dag.app.rm.LocalTaskSchedulerService$AsyncDelegateRequestHandler.run(LocalTaskSchedulerService.java:304)
>         at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to