[
https://issues.apache.org/jira/browse/MAPREDUCE-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618550#comment-13618550
]
Hadoop QA commented on MAPREDUCE-5066:
--------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12576324/MAPREDUCE-5066.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3484//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3484//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3484//console
This message is automatically generated.
> 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.patch,
> MAPREDUCE-5066.branch-1-win.2.patch, MAPREDUCE-5066.branch-1-win.3.patch,
> MAPREDUCE-5066.branch-1-win.patch, MAPREDUCE-5066.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
