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

Uma Maheswara Rao G commented on BOOKKEEPER-408:
------------------------------------------------

{noformat}
testOpenException                        =11.381s
testStreamingClients                     =9.793s
testReadWriteAsyncSingleClient           =7.660s
testReadWriteRangeAsyncSingleClient      =6.944s
testReadWriteAsyncSingleClientThrottle   =94.505s
testSyncReadAsyncWriteStringsSingleClient=10.330s
testReadWriteSyncSingleClient            =57.973s
testReadWriteZero                        =75.294s
testMultiLedger                          =128.302s
testReadWriteAsyncLength                 =6.218s
testShutdown                             =899.927s
testReadFromOpenLedger                   =32.631s
testReadFromOpenLedgerOpenOnce           =13.526s
testReadFromOpenLedgerZeroAndOne         =2.478s
testLastConfirmedAdd                     =67.694s
{noformat}

Here is the info ragarding time taken by each test in my local env.
                
> BookieReadWriteTest will enter the endless loop and will not leave out
> ----------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-408
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-408
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: bookkeeper-server
>    Affects Versions: 4.1.0
>         Environment: SUSE System
> ZooKeeper server
> three BookKeepers
>            Reporter: liuyang
>
> When I run the tests of BookKeeper, I found that the test running forever and 
> cannot be finished. The log has the exception that is 
> "junit.framework.AssertionFailedError: Return code is not OK: -6". 
> I thought this issuse might be come from the synchronization mechanism used 
> by the BookieReadWriteTest.
> for example in BookieReadWriteTest.TestReadWriteAsyncSingleClient()
> 1. when called the function lh.asyncAddEntry(entry.array(), this ,sync), the 
> call back function is addComplete(int, LedgerHandle, long, Object)
> 2. we can see that in addComplete(..) the function will be fail when rc != 
> BKException.Code.OK, and the x.counter++ will not be called never.
> 3. we assume that the function addComplete(..) is fail. so, in 
> TestReadWriteAsyncSingleClient(), the while loop enter endless loop because 
> sync.counter < numEntriesToWrite is right forever.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to