You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Devaraj K (JIRA)" <ji...@apache.org> on 2011/07/19 14:25:57 UTC

[jira] [Commented] (MAPREDUCE-1950) Jetty Acceptor can stuck TaskTracker forever

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067659#comment-13067659 ] 

Devaraj K commented on MAPREDUCE-1950:
--------------------------------------

As per jetty defect [JETTY-1251|http://jira.codehaus.org/browse/JETTY-1251], it is fixed in 6.1.25 version.


Can we upgrade to Jetty 6.1.25 or later version?

> Jetty Acceptor can stuck TaskTracker forever
> --------------------------------------------
>
>                 Key: MAPREDUCE-1950
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1950
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>    Affects Versions: 0.20.1
>            Reporter: Scott Chen
>            Assignee: Scott Chen
>
> We have observed some TaskTrackers keep getting blacklisted because of "Too many fetch-failure" and the logs are full of the following exception.
> There can be lots of these exceptions in one millisecond.
> {code}
> 2010-07-19 15:00:00,146 ERROR org.mortbay.log: EXCEPTION
> java.nio.channels.ClosedSelectorException
>         at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:66)
>         at sun.nio.ch.SelectorImpl.selectNow(SelectorImpl.java:88)
>         at org.mortbay.io.nio.SelectorManager$SelectSet.doSelect(SelectorManager.java:630)
>         at org.mortbay.io.nio.SelectorManager.doSelect(SelectorManager.java:191)
>         at org.mortbay.jetty.nio.SelectChannelConnector.accept(SelectChannelConnector.java:124)
>         at org.mortbay.jetty.AbstractConnector$Acceptor.run(AbstractConnector.java:708)
>         at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582)
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira