[
https://issues.apache.org/jira/browse/MAPREDUCE-3851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231549#comment-13231549
]
Robert Joseph Evans commented on MAPREDUCE-3851:
------------------------------------------------
The patch looks good to me. The only thing that I can think of might be
documentation. Do we want to have this documented? It will be removed in 0.23
when we no longer use Jetty so that makes me lean towards no, but the default
config value is to have this disabled
"mapreduce.reduce.shuffle.catch.exception.percent.limit.fatal" is 0.0 by
default. which if it is something that is off by default users who have this
problem will need to know how they can turn this on.
> 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.1.0, 1.0.1
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
