hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-139) Interrupted Exception within AsyncDispatcher leads to user confusion
Date Sat, 20 Oct 2012 01:00:29 GMT

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

Vinod Kumar Vavilapalli updated YARN-139:
-----------------------------------------

    Attachment: YARN-139-20121019.txt

bq. Tried out the patch, but it doesn't completely fix the problem. It does prevent spurious
exception traces in the handler threads when they are interrupted, but the exception trace
reported in the description is coming from the thread calling stop() on the AsyncDispatcher
service. It was interrupted while trying to join with the handling thread, and that exception
is still being logged.
I completely misread the JIRA description. Let's track the AsyncDispatcher logs separately.

Here's a patch to fix this. Can you please take a look?
                
> Interrupted Exception within AsyncDispatcher leads to user confusion
> --------------------------------------------------------------------
>
>                 Key: YARN-139
>                 URL: https://issues.apache.org/jira/browse/YARN-139
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: api
>    Affects Versions: 2.0.2-alpha, 0.23.4
>            Reporter: Nathan Roberts
>            Assignee: Vinod Kumar Vavilapalli
>         Attachments: YARN-139-20121019.txt, YARN-139.txt
>
>
> Successful applications tend to get InterruptedExceptions during shutdown. The exception
is harmless but it leads to lots of user confusion and therefore could be cleaned up.
> 2012-09-28 14:50:12,477 WARN [AsyncDispatcher event handler] org.apache.hadoop.yarn.event.AsyncDispatcher:
Interrupted Exception while stopping
> java.lang.InterruptedException
> 	at java.lang.Object.wait(Native Method)
> 	at java.lang.Thread.join(Thread.java:1143)
> 	at java.lang.Thread.join(Thread.java:1196)
> 	at org.apache.hadoop.yarn.event.AsyncDispatcher.stop(AsyncDispatcher.java:105)
> 	at org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:99)
> 	at org.apache.hadoop.yarn.service.CompositeService.stop(CompositeService.java:89)
> 	at org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobFinishEventHandler.handle(MRAppMaster.java:437)
> 	at org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobFinishEventHandler.handle(MRAppMaster.java:402)
> 	at org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.java:126)
> 	at org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:75)
> 	at java.lang.Thread.run(Thread.java:619)
> 2012-09-28 14:50:12,477 INFO [AsyncDispatcher event handler] org.apache.hadoop.yarn.service.AbstractService:
Service:Dispatcher is stopped.
> 2012-09-28 14:50:12,477 INFO [AsyncDispatcher event handler] org.apache.hadoop.yarn.service.AbstractService:
Service:org.apache.hadoop.mapreduce.v2.app.MRAppMaster is stopped.
> 2012-09-28 14:50:12,477 INFO [AsyncDispatcher event handler] org.apache.hadoop.mapreduce.v2.app.MRAppMaster:
Exiting MR AppMaster..GoodBye

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message