hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5066) JobTracker should set a timeout when calling into job.end.notification.url
Date Sat, 20 Apr 2013 19:27:17 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-5066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun C Murthy updated MAPREDUCE-5066:
-------------------------------------

          Resolution: Fixed
       Fix Version/s: 2.0.5-beta
                      1-win
                      1.2.0
    Target Version/s: 1.2.0, 1-win, 2.0.5-beta  (was: 1-win, 2.0.5-beta, 1.3.0)
              Status: Resolved  (was: Patch Available)

I just committed this. Thanks Ivan!
                
> 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
>             Fix For: 1.2.0, 1-win, 2.0.5-beta
>
>         Attachments: MAPREDUCE-5066.2.patch, MAPREDUCE-5066.3.patch, MAPREDUCE-5066.branch-1-win.2.patch,
MAPREDUCE-5066.branch-1-win.3.patch, MAPREDUCE-5066.branch-1-win.4.patch, MAPREDUCE-5066.branch-1-win.5.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

Mime
View raw message