[
https://issues.apache.org/jira/browse/HADOOP-6029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720466#action_12720466
]
Devaraj Das commented on HADOOP-6029:
-------------------------------------
Nicholas, can you please upload the logs of the test where you see
testReduceFromMem failing (as on the jira description).
Chris, we did read somewhere that maxMemory() is not necessarily a function of
-Xmx, and there are some quirks there. Let me try to get that link.
Counters added by HADOOP-2774 looks like a better candidate for the
TestReduceFetch use case.
> TestReduceFetch failed.
> -----------------------
>
> Key: HADOOP-6029
> URL: https://issues.apache.org/jira/browse/HADOOP-6029
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Tsz Wo (Nicholas), SZE
> Attachments:
> FAILING-PARTIALMEM-TEST-org.apache.hadoop.mapred.TestReduceFetch.txt,
> TEST-org.apache.hadoop.mapred.TestReduceFetch.txt,
> TEST-org.apache.hadoop.mapred.TestReduceFetch.txt
>
>
> {noformat}
> Testcase: testReduceFromMem took 23.625 sec
> FAILED
> Non-zero read from local: 83
> junit.framework.AssertionFailedError: Non-zero read from local: 83
> at
> org.apache.hadoop.mapred.TestReduceFetch.testReduceFromMem(TestReduceFetch.java:289)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> {noformat}
> Ran TestReduceFetch a few times on a clean trunk. It failed consistently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
