Hadoop-Mapreduce-trunk - Build # 1373 - Failure

[Apache Jenkins Server]

See https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1373/

###
## LAST 60 LINES OF THE CONSOLE 
###
[...truncated 28799 lines...]
Running org.apache.hadoop.mapreduce.jobhistory.TestJobHistoryEventHandler
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.144 sec

Results :

Failed tests:   
testMultipleCrashes(org.apache.hadoop.mapreduce.v2.app.TestRecovery): Reduce 
Task state not correct expected:RUNNING but was:SCHEDULED
  testOutputRecovery(org.apache.hadoop.mapreduce.v2.app.TestRecovery): Task 
state is not correct (timedout) expected:SUCCEEDED but was:RUNNING
  testOutputRecoveryMapsOnly(org.apache.hadoop.mapreduce.v2.app.TestRecovery): 
Task state is not correct (timedout) expected:SUCCEEDED but was:RUNNING
  testRecoveryWithOldCommiter(org.apache.hadoop.mapreduce.v2.app.TestRecovery): 
Task state is not correct (timedout) expected:SUCCEEDED but was:RUNNING
  testSpeculative(org.apache.hadoop.mapreduce.v2.app.TestRecovery): Task state 
is not correct (timedout) expected:SUCCEEDED but was:RUNNING

Tests run: 209, Failures: 5, Errors: 0, Skipped: 0

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] hadoop-mapreduce-client ... SUCCESS [1.699s]
[INFO] hadoop-mapreduce-client-core .. SUCCESS [23.306s]
[INFO] hadoop-mapreduce-client-common  SUCCESS [22.849s]
[INFO] hadoop-mapreduce-client-shuffle ... SUCCESS [1.796s]
[INFO] hadoop-mapreduce-client-app ... FAILURE [5:23.075s]
[INFO] hadoop-mapreduce-client-hs  SKIPPED
[INFO] hadoop-mapreduce-client-jobclient . SKIPPED
[INFO] hadoop-mapreduce-client-hs-plugins  SKIPPED
[INFO] Apache Hadoop MapReduce Examples .. SKIPPED
[INFO] hadoop-mapreduce .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 6:13.295s
[INFO] Finished at: Fri Mar 15 13:20:44 UTC 2013
[INFO] Final Memory: 20M/128M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.12.3:test (default-test) on 
project hadoop-mapreduce-client-app: There are test failures.
[ERROR] 
[ERROR] Please refer to 
/home/jenkins/jenkins-slave/workspace/Hadoop-Mapreduce-trunk/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app/target/surefire-reports
 for the individual test results.
[ERROR] - [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn goals -rf :hadoop-mapreduce-client-app
Build step 'Execute shell' marked build as failure
[FINDBUGS] Skipping publisher since build result is FAILURE
Archiving artifacts
Updating HDFS-4596
Updating HDFS-3367
Updating HADOOP-9405
Updating HADOOP-9406
Updating YARN-237
Updating HADOOP-9407
Updating YARN-468
Updating HDFS-3277
Email was triggered for: Failure
Sending email for trigger: Failure



###
## FAILED TESTS (if any) 
##
No tests ran.

[jira] [Created] (MAPREDUCE-5074) Remove limits on number of counters and counter groups in MapReduce

[Ravi Prakash (JIRA)]

Ravi Prakash created MAPREDUCE-5074:
---

 Summary: Remove limits on number of counters and counter groups in 
MapReduce
 Key: MAPREDUCE-5074
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5074
 Project: Hadoop Map/Reduce
  Issue Type: Improvement
  Components: mr-am, mrv2
Affects Versions: 2.0.3-alpha, 3.0.0, 0.23.6
Reporter: Ravi Prakash


Can we please consider removing limits on the number of counters and counter 
groups now that it is all user code? Thanks to the much better architecture of 
YARN in which there is no single Job Tracker we have to worry about 
overloading, I feel we should do away with this (now arbitrary) constraint on 
users' capabilities. Thoughts?

--
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] [Created] (MAPREDUCE-5075) DistCp leaks input file handles

[Chris Nauroth (JIRA)]

Chris Nauroth created MAPREDUCE-5075:


 Summary: DistCp leaks input file handles
 Key: MAPREDUCE-5075
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5075
 Project: Hadoop Map/Reduce
  Issue Type: Bug
  Components: distcp
Affects Versions: 3.0.0
Reporter: Chris Nauroth
Assignee: Chris Nauroth


DistCp wraps the {{InputStream}} for each input file it reads in an instance of 
{{ThrottledInputStream}}.  This class does not close the wrapped 
{{InputStream}}.  {{RetriableFileCopyCommand}} guarantees that the 
{{ThrottledInputStream}} gets closed, but without closing the underlying 
wrapped stream, it still leaks a file handle.

--
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] [Created] (MAPREDUCE-5076) CombineFileInputFormat with maxSplitSize can omit data

[Sandy Ryza (JIRA)]

Sandy Ryza created MAPREDUCE-5076:
-

 Summary: CombineFileInputFormat with maxSplitSize can omit data
 Key: MAPREDUCE-5076
 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5076
 Project: Hadoop Map/Reduce
  Issue Type: Bug
Reporter: Sandy Ryza
Assignee: Sandy Ryza


I ran a local job with CombineFileInputFormat using an 80 MB file and a max 
split size of 32 MB (the default local FS block size).  The job ran with two 
splits of 32 MB, and the last 16 MB were just omitted.

This appears to be caused by a subtle bug in getMoreSplits, in which the code 
that generates the splits from the blocks expects the 16 MB block to be at the 
end of the block list. But the code that generates the blocks does not respect 
this.

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