[
https://issues.apache.org/jira/browse/MAPREDUCE-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803103#action_12803103
]
Aaron Kimball commented on MAPREDUCE-1392:
------------------------------------------
On one of our QA clusters, we see consistent failure of
TestReduceFetch.testReduceFromPartialMem(). A git-bisect revealed that the
original test as added by HADOOP-3446 passes, but the "fix" implemented in
HADOOP-4302 causes it to fail. Note that other machines (both 32- and 64-bit)
do not experience the test failure.
The dialogue in HADOOP-4302 says that the test is still race-prone, and that
the "fix" in HADOOP-4302 tweaked some parameters in an attempt to make such
conditions less likely. Is it possible to move these parameters into a better
position that would make this even less likely? (I don't fully understand the
relationship between them all and this test.)
Ultimately, it would be good to completely refactor the test into one that's
deterministic. As is, it's hard to tell what we learn from a failure in this
test suite.
> TestReduceFetch failure
> -----------------------
>
> Key: MAPREDUCE-1392
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1392
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Affects Versions: 0.20.1
> Environment: $ uname -a
> Linux monster03.sf.cloudera.com 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT
> 2009 x86_64 x86_64 x86_64 GNU/Linux
> $ java -version
> java version "1.6.0_14"
> Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
> Java HotSpot(TM) 64-Bit Server VM (build 14.0-b16, mixed mode)
> Reporter: Aaron Kimball
>
> TestReduceFetch is failing on one of our QA machines
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
