[
https://issues.apache.org/jira/browse/HBASE-10142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852106#comment-13852106
]
Ted Yu commented on HBASE-10142:
--------------------------------
>From https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/8/console :
{code}
Running org.apache.hadoop.hbase.regionserver.wal.TestLogRolling
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 833.809 sec
{code}
>From https://builds.apache.org/job/HBase-TRUNK/4735/console :
{code}
Running org.apache.hadoop.hbase.regionserver.wal.TestLogRolling
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 440.048 sec
{code}
Looks like the test runs 2x slower on hadoop 1.1
> 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
> Assignee: Ted Yu
> Fix For: 0.98.0
>
> Attachments: 10142-v1.txt
>
>
> 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 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)
