[jira] [Commented] (MAPREDUCE-5128) mapred-default.xml is missing a bunch of history server configs

2013-04-18 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635077#comment-13635077
 ] 

Hudson commented on MAPREDUCE-5128:
---

Integrated in Hadoop-Yarn-trunk #187 (See 
[https://builds.apache.org/job/Hadoop-Yarn-trunk/187/])
MAPREDUCE-5128. mapred-default.xml is missing a bunch of history server 
configs. (sandyr via tucu) (Revision 1469095)

 Result = FAILURE
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1469095
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml


 mapred-default.xml is missing a bunch of history server configs
 ---

 Key: MAPREDUCE-5128
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5128
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: documentation, jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.5-beta

 Attachments: MAPREDUCE-5128.patch


 mapred-default.xml is missing many configs that work for the job history 
 server.  mapreduce.jobhistory.cleaner.enable, mapreduce.jobhistory.done-dir, 
 and mapreduce.jobhistory.datestring.cache.size are a few examples.

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


[jira] [Commented] (MAPREDUCE-5128) mapred-default.xml is missing a bunch of history server configs

2013-04-18 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635133#comment-13635133
 ] 

Hudson commented on MAPREDUCE-5128:
---

Integrated in Hadoop-Hdfs-trunk #1376 (See 
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1376/])
MAPREDUCE-5128. mapred-default.xml is missing a bunch of history server 
configs. (sandyr via tucu) (Revision 1469095)

 Result = FAILURE
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1469095
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml


 mapred-default.xml is missing a bunch of history server configs
 ---

 Key: MAPREDUCE-5128
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5128
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: documentation, jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.5-beta

 Attachments: MAPREDUCE-5128.patch


 mapred-default.xml is missing many configs that work for the job history 
 server.  mapreduce.jobhistory.cleaner.enable, mapreduce.jobhistory.done-dir, 
 and mapreduce.jobhistory.datestring.cache.size are a few examples.

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


[jira] [Commented] (MAPREDUCE-5128) mapred-default.xml is missing a bunch of history server configs

2013-04-18 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13635176#comment-13635176
 ] 

Hudson commented on MAPREDUCE-5128:
---

Integrated in Hadoop-Mapreduce-trunk #1403 (See 
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1403/])
MAPREDUCE-5128. mapred-default.xml is missing a bunch of history server 
configs. (sandyr via tucu) (Revision 1469095)

 Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1469095
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml


 mapred-default.xml is missing a bunch of history server configs
 ---

 Key: MAPREDUCE-5128
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5128
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: documentation, jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.5-beta

 Attachments: MAPREDUCE-5128.patch


 mapred-default.xml is missing many configs that work for the job history 
 server.  mapreduce.jobhistory.cleaner.enable, mapreduce.jobhistory.done-dir, 
 and mapreduce.jobhistory.datestring.cache.size are a few examples.

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


[jira] [Commented] (MAPREDUCE-5128) mapred-default.xml is missing a bunch of history server configs

2013-04-17 Thread Alejandro Abdelnur (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634545#comment-13634545
 ] 

Alejandro Abdelnur commented on MAPREDUCE-5128:
---

+1

 mapred-default.xml is missing a bunch of history server configs
 ---

 Key: MAPREDUCE-5128
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5128
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: documentation, jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Attachments: MAPREDUCE-5128.patch


 mapred-default.xml is missing many configs that work for the job history 
 server.  mapreduce.jobhistory.cleaner.enable, mapreduce.jobhistory.done-dir, 
 and mapreduce.jobhistory.datestring.cache.size are a few examples.

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


[jira] [Commented] (MAPREDUCE-5128) mapred-default.xml is missing a bunch of history server configs

2013-04-17 Thread Hudson (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634598#comment-13634598
 ] 

Hudson commented on MAPREDUCE-5128:
---

Integrated in Hadoop-trunk-Commit #3625 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/3625/])
MAPREDUCE-5128. mapred-default.xml is missing a bunch of history server 
configs. (sandyr via tucu) (Revision 1469095)

 Result = SUCCESS
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1469095
Files : 
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core/src/main/resources/mapred-default.xml


 mapred-default.xml is missing a bunch of history server configs
 ---

 Key: MAPREDUCE-5128
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5128
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: documentation, jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Fix For: 2.0.5-beta

 Attachments: MAPREDUCE-5128.patch


 mapred-default.xml is missing many configs that work for the job history 
 server.  mapreduce.jobhistory.cleaner.enable, mapreduce.jobhistory.done-dir, 
 and mapreduce.jobhistory.datestring.cache.size are a few examples.

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


[jira] [Commented] (MAPREDUCE-5128) mapred-default.xml is missing a bunch of history server configs

2013-04-04 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/MAPREDUCE-5128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13622855#comment-13622855
 ] 

Hadoop QA commented on MAPREDUCE-5128:
--

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12577069/MAPREDUCE-5128.patch
  against trunk revision .

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:green}+0 tests included{color}.  The patch appears to be a 
documentation patch that doesn't require tests.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

{color:green}+1 eclipse:eclipse{color}.  The patch built with 
eclipse:eclipse.

{color:green}+1 findbugs{color}.  The patch does not introduce any new 
Findbugs (version 1.3.9) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:green}+1 core tests{color}.  The patch passed unit tests in 
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.

{color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3497//testReport/
Console output: 
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3497//console

This message is automatically generated.

 mapred-default.xml is missing a bunch of history server configs
 ---

 Key: MAPREDUCE-5128
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5128
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: documentation, jobhistoryserver
Affects Versions: 2.0.3-alpha
Reporter: Sandy Ryza
Assignee: Sandy Ryza
 Attachments: MAPREDUCE-5128.patch


 mapred-default.xml is missing many configs that work for the job history 
 server.  mapreduce.jobhistory.cleaner.enable, mapreduce.jobhistory.done-dir, 
 and mapreduce.jobhistory.datestring.cache.size are a few examples.

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