[MAPREDUCE-3427] streaming tests fail with MR2

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.23.1, 2.0.0-alpha
• Fix Version/s: 0.23.1
• Component/s: contrib/streaming, mrv2
• Assignee: Hitesh Shah
• Reporter: Alejandro Abdelnur
• Created: 18/Nov/11 04:41
• Updated: 10/Mar/15 04:31
• Resolved: 01/Feb/12 23:06

Description

After Mavenizing streaming and getting its testcases to use the MiniMRCluster wrapper (MAPREDUCE-3169), 4 testcases fail to pass.

Following is an assessment of those failures. Note that the testcases have been tweaked only to set the streaming JAR and yarn as the framework.

(If these issues are unrelated we should create sub-tasks for each one of them).

TestStreamingCombiner, fails because returned counters don't match assertion. However, counters printed in the test output indicate values that would satisfy the assertion. As Tom has indicated it seems MR/YARN are not passing back counter information to the client API.

TestStreamingBadRecords, the job is failing with the following exception

Application application_1321575850006_0001 failed 1 times due to AM Container for 
appattempt_1321575850006_0001_000001 exited with  exitCode: 127 due to: 
.Failing this attempt.. Failing the application.

Difficult to troubleshoot because there are not task logs from Mini MR/YARN run.

TestStreamingStatus fails in validateTaskStatus() in the following assertion

expected:<[before consuming input > sort]> but was:<[SUCCEEDED]>

TestUlimit fails with

org.junit.ComparisonFailure: output is wrong expected:<[786432]> but was:<[unlimited]>

Issue Links

• breaks: HADOOP-7590 Mavenize streaming and MR examples
• is blocked by: MAPREDUCE-3409 Incorrect custom task status when running on MR2

Sub-Tasks

• Finding counters by legacy group name returns empty counters: Closed