[
https://issues.apache.org/jira/browse/BOOKKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flavio Junqueira reopened BOOKKEEPER-29:
----------------------------------------
Assignee: Flavio Junqueira
This test still fails for me intermittently, but I think I have been able to
nail it down. The main problem seems to be with BookieWatcher. To obtain a new
bookie for an open ledger, we request it from BookieWatcher. It is possible,
though, that we see a new bookie registered with ZooKeeper (as in
stateNewBookie), but the notification of the change in ZooKeeper has not been
processed by BookieWatcher yet. In this case, we close the ledger because we
can't get a new bookie, and the test fails.
To solve this problem, we need to force an update to the list of the
BookieWatcher object.
> BookieRecoveryTest fails intermittently
> ---------------------------------------
>
> Key: BOOKKEEPER-29
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-29
> Project: Bookkeeper
> Issue Type: Bug
> Reporter: Ivan Kelly
> Assignee: Flavio Junqueira
> Fix For: 3.4.0
>
> Attachments: BK-29.diff, BK-29.diff, BK-29.diff, BK-29.diff,
> BOOKKEEPER-29.patch, BOOKKEEPER-29.patch,
> 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
