[
https://issues.apache.org/jira/browse/BOOKKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078427#comment-13078427
]
Flavio Junqueira commented on BOOKKEEPER-29:
--------------------------------------------
It's nice that you've been able to find the problem, Ivan. Two comments:
# It doesn't look like moving the start of a new bookie up solves completely
the problem, since we are still not sure that the bookie has registered. It is
true that we are giving more time, but in my understanding we are just reducing
the chance that it happens and not eliminating it. We probably need to watch
the list of bookies on ZooKeeper to be able to determine when the list changes;
# There is a change to the log4j.properties that shouldn't be there.
> 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
