hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ravi Prakash (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3028) Support job end notification in .next /0.23
Date Thu, 20 Oct 2011 23:50:10 GMT

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

Ravi Prakash commented on MAPREDUCE-3028:
-----------------------------------------

@Hitesh: I gathered requirements from a couple of folks at Yahoo! This was one dream / wish.
I'll ask them again where it could be helpful if you want. In any case, if you don't want
to use it (which is the default), you only have to not specify "mapreduce.job.end-notification.url.separator.regex".


The openConnection only returns a URLConnection object. I agree its ambiguously named. In
fact that is the only way to get a URLConnection object I know. Quoting http://download.oracle.com/javase/6/docs/api/java/net/URLConnection.html

# The connection object is created by invoking the openConnection method on a URL.
# The setup parameters and general request properties are manipulated.
# The actual connection to the remote object is made, using the connect method.
# The remote object becomes available. The header fields and the contents of the remote object
can be accessed. 


                
> Support job end notification in .next /0.23
> -------------------------------------------
>
>                 Key: MAPREDUCE-3028
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3028
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Mohammad Kamrul Islam
>            Assignee: Ravi Prakash
>            Priority: Blocker
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-3028.branch-0.23.patch, MAPREDUCE-3028.patch, MAPREDUCE-3028.patch
>
>
> Oozie primarily depends on  the job end notification to determine when the job finishes.
In the current version,  job end notification is implemented in job tracker. Since job tracker
will be removed in the upcoming hadoop release (.next), we wander where this support will
move. I think this best effort notification could be implemented in the new Application Manager
as one of the last step of job completion.
> Whatever implementation will it be, Oozie badly needs this feature to be continued in
next releases as well.
>  

--
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

        

Mime
View raw message