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

["Olga Shen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542053#comment-13542053 ] 

Olga Shen commented on MAPREDUCE-1688:
--------------------------------------

MAPREDUCE-3028 only added timeout setting in org.apache.hadoop.mapreduce.v2.app.JobEndNotifier.
Would you apply timeout setting to org.apache.hadoop.mapred.JobEndNotifier for MRv1 users?
                
> 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, 1.0.0, 1.0.2, 1.0.3
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Ravi Prakash
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira