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

ASF GitHub Bot commented on BOOKKEEPER-1004:
--------------------------------------------

Github user govind-menon commented on the issue:

    https://github.com/apache/bookkeeper/pull/109
  
    The current test failures - 
org.apache.bookkeeper.client.BookieRecoveryTest.ensurePasswordUsedForOldLedgers[4]
    
org.apache.bookkeeper.client.BookieRecoveryTest.ensurePasswordUsedForOldLedgers[5]
 
    
    will be fixed in another JIRA.


> Allow bookie garbage collection to be triggered manually from tests
> -------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-1004
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1004
>             Project: Bookkeeper
>          Issue Type: Improvement
>          Components: bookkeeper-server
>    Affects Versions: 4.5.0, 4.6.0
>            Reporter: Govind Menon
>            Priority: Minor
>              Labels: test
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> The current gc tests rely on waiting on a timeout for gc to run. It's
> never certain whether it has run or not or if it's still running. 
> This patch allows tests to trigger a gc run and gives the client
> a future to know when it has completed. The gc algorithm is unchangedI but 
> now it runs in a scheduled executor rather than as a
> Thread.
> This work was originally done by Ivan Kelly and I am just pushing it back to 
> open source



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to