Description
Add S3A tests to run terasort for the magic and directory committers.
MAPREDUCE-7091 is a requirement for this
Bonus feature: print the results to see which committers are faster in the specific test setup. As that's a function of latency to the store, bandwidth and size of jobs, it's not at all meaningful, just interesting.
Attachments
Attachments
Issue Links
- causes
-
HADOOP-16357 TeraSort Job failing on S3 DirectoryStagingCommitter: destination path exists
- Resolved
- contains
-
MAPREDUCE-7090 BigMapOutput example doesn't work with paths off cluster fs
- Resolved
-
MAPREDUCE-7091 Terasort on S3A to switch to new committers
- Resolved
-
MAPREDUCE-7092 MR examples to work better against cloud stores
- Resolved
- depends upon
-
MAPREDUCE-7099 Daily test result fails in MapReduce JobClient though there isn't any error
- Reopened
- incorporates
-
HADOOP-15890 Some S3A committer tests don't match ITest* pattern; don't run in maven
- Resolved
-
MAPREDUCE-7090 BigMapOutput example doesn't work with paths off cluster fs
- Resolved
-
MAPREDUCE-7091 Terasort on S3A to switch to new committers
- Resolved
-
MAPREDUCE-7092 MR examples to work better against cloud stores
- Resolved
- is duplicated by
-
HADOOP-16153 Allow TeraGen to use schema-specific output committer
- Resolved
- links to