[
https://issues.apache.org/jira/browse/BOOKKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-29:
---------------------------------
Attachment: BOOKKEEPER-29.patch
1. Removed public method from BookKeeper
2. Removed redundant calls to new BookKeeper in Bookie. Its already done by the
base class.
3. Added synchronization on PerChannelBookieClient#connect
I ran this patch in a loop for 3 hours at while point it hit the netty cleanup
hang. 2. & 3. should help with this, though it's hard to find the root cause as
a repro takes 3 hours.
> 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-v2.patch, BOOKKEEPER-29.patch, 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
