You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2013/12/16 01:39:07 UTC
[jira] [Commented] (HBASE-10142)
TestLogRolling#testLogRollOnDatanodeDeath test failure
[ https://issues.apache.org/jira/browse/HBASE-10142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848730#comment-13848730 ]
Andrew Purtell commented on HBASE-10142:
----------------------------------------
The Jenkins slaves running this test were JDK 6. I've updated them to JDK 7u45 along with other build infrastructure and am retesting. Locally I cannot reproduce this problem after 20 iterations, continuing to 100.
> TestLogRolling#testLogRollOnDatanodeDeath test failure
> ------------------------------------------------------
>
> Key: HBASE-10142
> URL: https://issues.apache.org/jira/browse/HBASE-10142
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0, 0.99.0
> Reporter: Andrew Purtell
> Fix For: 0.98.0
>
>
> This is a demanding unit test, which fails fairly often as software versions (JVM, Hadoop) and system load change. Currently when testing 0.98 branch using Oracle JRE 1.7.0u45 I see this failure:
> {noformat}
> Failed tests: testLogRollOnDatanodeDeath(org.apache.hadoop.hbase.regionserver.wal.TestLogRolling): LowReplication Roller should've been disabled, current replication=1
> {noformat}
> Could be a timing issue after the recent switch to Hadoop 2 as default build/test profile. Let's see if more leniency makes sense and if it can stabilize the test before disabling it.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)