[
https://issues.apache.org/jira/browse/MAPREDUCE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ravi Prakash resolved MAPREDUCE-1688.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.23.1
Assignee: Ravi Prakash
This has been fixed by MAPREDUCE-3028. Since each AM is now doing the job-end
notification, it has automatically been parallelized. Also, timeouts have been
set in the HttpURLConnection object.
> A failing retry'able notification in JobEndNotifier can affect notifications
> of other jobs.
> -------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1688
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1688
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.1
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Ravi Prakash
> Fix For: 0.23.1
>
>
> The JobTracker puts all the notification commands into a delay-queue. It has
> a single thread that loops through this queue and sends out the
> notifications. When it hits failures with any notification which is
> configured to be retired via {{job.end.retry.attempts}} and
> {{job.end.retry.interval}}, the notification is queued back again. A single
> notification with sufficiently large number of configured retries and which
> consistently fails will affect other notifications in the queue.
--
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
