hadoop-mapreduce-issues mailing list archives

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

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

jiraposter@reviews.apache.org commented on MAPREDUCE-3028:
----------------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2468/#review2727
-----------------------------------------------------------



branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/JobEndNotifier.java
<https://reviews.apache.org/r/2468/#comment6133>

    The Javadocs is not completely correct, it does not return the URLs (This is really minor)



branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestJobEndNotifier.java
<https://reviews.apache.org/r/2468/#comment6134>

    It is not that common of a practice to have your test extend what it is testing.  I don't
think it is bad, I just think it would be more accepted, if you made the values you want to
access package, instead of protected, or if you added in getters for those values.



branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestJobEndNotifier.java
<https://reviews.apache.org/r/2468/#comment6135>

    Just a note that this can be done with mockito and spy instead of overriding this directly,
so you would not have to subclass the original class.



branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRJobConfig.java
<https://reviews.apache.org/r/2468/#comment6136>

    Removing/Renaming these values breaks binary compatibility and source compatibility. Even
if the name is not that clean it is best to leave it alone.  If you must rename it then @Deprecate
the old ones, have them point to the new ones, and then file a JIRA to remove the old ones
in a release or two, to give people time to update their code.


- Robert


On 2011-10-20 21:09:33, Ravi Prakash wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/2468/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2011-10-20 21:09:33)
bq.  
bq.  
bq.  Review request for Tom Graves, Robert Evans, Jonathan Eagles, and Mark Holderbaugh.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Job end notification for 0.23 / next. I'm going to work on unit tests while you folks
review the code.
bq.  
bq.  The only new thing added to 0.20 is that multiple recipients can be configured to receive
the job-end notification by supplying multiple URLs (one parameter separated by a regex)
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/JobEndNotifier.java
PRE-CREATION 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/MRAppMaster.java
1186838 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestJobEndNotifier.java
PRE-CREATION 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobConf.java
1186838 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapred/JobEndNotifier.java
1186838 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/MRJobConfig.java
1186838 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/java/org/apache/hadoop/mapreduce/util/ConfigUtil.java
1186838 
bq.    branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml
1186838 
bq.  
bq.  Diff: https://reviews.apache.org/r/2468/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  Manually tested changes on a single node cluster. Going to add unit tests.
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Ravi
bq.  
bq.


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