[
https://issues.apache.org/jira/browse/MAPREDUCE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855500#action_12855500
]
Vinod K V commented on MAPREDUCE-1688:
--------------------------------------
Clearly, one job's notification shouldn't affect another's - so we will need
separate threads for each notification(from a thread pool?). We should also put
caps on the {{retry.attempts}} and {{retry.interval}}. We should also log when
a notification is finally sent out successfully.
> 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 K V
>
> 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.
-
You can reply to this email to add a comment to the issue online.
