[
https://issues.apache.org/jira/browse/MAPREDUCE-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615753#comment-13615753
]
Arun C Murthy commented on MAPREDUCE-5066:
------------------------------------------
Ivan - the patch looks good. You'll need to port this to branch-1 and
branch-2(trunk).
Also, if you could minimize formatting changes it will make it easier to review
(for future ref). Thanks!
> JobTracker should set a timeout when calling into job.end.notification.url
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-5066
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5066
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 1-win, 2.0.3-alpha, 1.3.0
> Reporter: Ivan Mitic
> Assignee: Ivan Mitic
> Attachments: MAPREDUCE-5066.branch-1-win.2.patch,
> MAPREDUCE-5066.branch-1-win.patch
>
>
> In current code, timeout is not specified when JobTracker (JobEndNotifier)
> calls into the notification URL. When the given URL points to a server that
> will not respond for a long time, job notifications are completely stuck
> (given that we have only a single thread processing all notifications). We've
> seen this cause noticeable delays in job execution in components that rely on
> job end notifications (like Oozie workflows).
> I propose we introduce a configurable timeout option and set a default to a
> reasonably small value.
> If we want, we can also introduce a configurable number of workers processing
> the notification queue (not sure if this is needed though at this point).
> I will prepare a patch soon. Please comment back.
--
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
