[
https://issues.apache.org/jira/browse/BOOKKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078471#comment-13078471
]
Ivan Kelly commented on BOOKKEEPER-29:
--------------------------------------
1. The scenario is something that should never happen in the wild. Usually a
cluster will be have all machines started before the failure even happens. The
only reason the recovery server is started later in this case is so that it
doesn't become part of the original ensemble.
I think just putting the start server earlier is enough, because there are many
calls to bk after this. This mean the test thread will be preempted and the zk
watcher thread will get a chance to run, updating the available server lists.
The other option may be to do zk sync explicitly after the newServer call. I
don't think it add anything though.
2. this is a mistake, i generated the patch wrong. reattached a new one.
> 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, 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
