[ 
https://issues.apache.org/jira/browse/HBASE-10142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13854662#comment-13854662
 ] 

Enis Soztutar commented on HBASE-10142:
---------------------------------------

Run the test 12 times on my windows box. failed only once with: 
{code}
Failed tests:   
testLogRollOnDatanodeDeath(org.apache.hadoop.hbase.regionserver.wal.TestLogRolling):
 New log file should have the default replication instead of 1
{code}

This is definitely an improvement over a failure every other time. I would 
suggest we pick this patch for 0.96 as well. Though the writer vs tmpWriter is 
a bit different in 0.96 than trunk. 



> 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, 0.99.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)

Reply via email to