[ 
https://issues.apache.org/jira/browse/BOOKKEEPER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079091#comment-13079091
 ] 

Ivan Kelly commented on BOOKKEEPER-29:
--------------------------------------

Sync solution doesn't work. I added 
{code}

        final CountDownLatch latch = new CountDownLatch(1);
        bkc.getZkHandle().sync("/", new VoidCallback() {
                public void processResult(int rc, String path, Object ctx) {
                    latch.countDown();
                }
            }, null);
        latch.await();

{code}

to #startNewBookie (I left the calls to this method in their original places). 
It doesn't ensure the watcher is run. 

Im trying with simply Thread.yield() to see if that does any better.

> 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

        

Reply via email to