[
https://issues.apache.org/jira/browse/MAPREDUCE-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13445548#comment-13445548
]
Todd Lipcon commented on MAPREDUCE-3851:
----------------------------------------
[~tgraves], I finally figured out the bug that causes the acceptors to
occasionally not start. It's JETTY-1316. I pushed a patched jetty here:
https://github.com/toddlipcon/jetty-hadoop-fix/
and we'll try to deploy it to our maven repository as 6.1.26.cloudera.2 soon.
Hope this helps!
> Allow more aggressive action on detection of the jetty issue
> ------------------------------------------------------------
>
> Key: MAPREDUCE-3851
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3851
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 1.0.0
> Reporter: Kihwal Lee
> Assignee: Thomas Graves
> Fix For: 1.0.2
>
> Attachments: MAPREDUCE-3851.patch, MAPREDUCE-3851.patch,
> MAPREDUCE-3851.patch, MAPREDUCE-3851.patch
>
>
> MAPREDUCE-2529 added the useful failure detection mechanism. In this jira, I
> propose we add a periodic check inside TT and configurable action to
> self-destruct. Blacklisting helps but is not enough. Hung jetty still accepts
> connection and it takes very long time for clients to fail out. Short jobs
> are delayed for hours because of this. This feature will be a nice companion
> to MAPREDUCE-3184.
--
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
