[MAPREDUCE-1688] A failing retry'able notification in JobEndNotifier can affect notifications of other jobs.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.20.1, 1.0.0, 1.0.2, 1.0.3
• Component/s: jobtracker
• Assignee: Ravi Prakash
• Reporter: Vinod Kumar Vavilapalli
• Created: 09/Apr/10 17:56
• Updated: 01/Feb/13 03:20
• Resolved: 21/Feb/12 22:07

Description

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.

Issue Links

• relates to: MAPREDUCE-4935 Support timeout limitation to MRv1 job end notifications
• relates to: MAPREDUCE-3028 Support job end notification in .next /0.23