[
https://issues.apache.org/jira/browse/MAPREDUCE-4786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496176#comment-13496176
]
Hudson commented on MAPREDUCE-4786:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #1225 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1225/])
MAPREDUCE-4786. Job End Notification retry interval is 5 milliseconds by
default (Ravi Prakash via bobby) (Revision 1408444)
Result = SUCCESS
bobby : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1408444
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/main/java/org/apache/hadoop/mapreduce/v2/app/JobEndNotifier.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/src/test/java/org/apache/hadoop/mapreduce/v2/app/TestJobEndNotifier.java
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml
> Job End Notification retry interval is 5 milliseconds by default
> ----------------------------------------------------------------
>
> Key: MAPREDUCE-4786
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4786
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2
> Affects Versions: 3.0.0, 2.0.2-alpha, 0.23.4
> Reporter: Ravi Prakash
> Assignee: Ravi Prakash
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> Attachments: MAPREDUCE-4786.branch-2.patch,
> MAPREDUCE-4786.branch-2.patch, MAPREDUCE-4786.patch, MAPREDUCE-4786.patch,
> MAPREDUCE-4786.patch
>
>
> Courtesy [~stevenwillis] and [~qwertymaniac]
> {quote}
> From: Harsh J
> I believe the configs of the latter of both of the above
> classifications were meant to be added in as replacement names, but
> the property names got added in wrong (as the former/older named ones)
> in the XML.
> the word "seconds" in the description of retries? The code in MR2's
> JobEndNotifier seems to expect seconds but uses it directly in
> Thread.sleep(…) without making it milliseconds, which may be a bug we
> need to fix as well, perhaps in a same issue as the configs ones.
> On Fri, Nov 9, 2012 at 11:21 PM, Steven Willis <swil...@compete.com> wrote:
> > And I noticed that there are some duplicate properties with different
> > values and different descriptions:
> {quote}
--
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
