[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ivan Kelly updated BOOKKEEPER-29:
---------------------------------

    Attachment: BK-29.diff

The problem was in the test. The tests created a bunch of bookies, and wrote a 
load of entries and failed the server. They then created a new server and tried 
to verify the recovered ledger. The problem was that there was no time between 
creating the server and trying to verify, which meant that the watcher on the 
client may not have been updated with the full bookie list. This meant that a 
full ensemble could not be built and the test failed at that point. This patch 
fixes that by moving the creation of the new server to earlier in the test, 
before the entries are written but after the initial ledger handle is created.

> BookieRecoveryTest fails intermittently
> ---------------------------------------
>
>                 Key: BOOKKEEPER-29
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-29
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>             Fix For: 3.4.0
>
>         Attachments: BK-29.diff, 
> org.apache.bookkeeper.test.BookieRecoveryTest.txt
>
>
> The failure doesn't hit every time. You have to run, multiple times. From 
> bookkeeper-server, run mvn test -Dtest=BookieRecoveryTest multiple times to 
> repro.
> Test output is attached.
> -------------------------------------------------------
>  T E S T S
> -------------------------------------------------------
> Running org.apache.bookkeeper.test.BookieRecoveryTest
> log4j:WARN No appenders could be found for logger 
> (org.apache.bookkeeper.test.BaseTestCase).
> log4j:WARN Please initialize the log4j system properly.
> Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.794 sec <<< 
> FAILURE!
> Results :
> Tests in error: 
>   
> testAsyncBookieRecoveryToSpecificBookie[1](org.apache.bookkeeper.test.BookieRecoveryTest)
> Tests run: 8, Failures: 0, Errors: 1, Skipped: 0

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to