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

Hudson commented on MAPREDUCE-3028:
-----------------------------------

Integrated in Hadoop-Hdfs-trunk-Commit #1231 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1231/])
    MAPREDUCE-3263. Fixed the MAPREDUCE-3028 commit which broke MR1. 
Contributed by Hitesh Shah.

acmurthy : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1188997
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/src/test/mapred/org/apache/hadoop/mapred/NotificationTestCase.java

                
> 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, MAPREDUCE-3028.patch, MAPREDUCE-3028.patch, 
> MAPREDUCE-3028.patch, RMContainerAllocator.diff
>
>
> 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

        

Reply via email to