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

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

GitHub user sid825 opened a pull request:

    https://github.com/apache/bookkeeper/pull/13

    BOOKKEEPER-892: Bookie sanity test

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sid825/bookkeeper BOOKKEEPER-892

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/bookkeeper/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #13
    
----
commit cbde087f18bff558d64b7ce39850f8d92a7a9e8d
Author: Siddharth Boobna <[email protected]>
Date:   2016-02-08T03:07:31Z

    BOOKKEEPER-892: Bookie sanity test
    
    Change-Id: I194a643fe72d92ff16bd63a1f002fabd36224baa

----


> Add a sanity test to help identify bookie nodes with problems that prevent 
> writes but is still registered in ZK
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-892
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-892
>             Project: Bookkeeper
>          Issue Type: Test
>          Components: bookkeeper-server
>    Affects Versions: 4.3.2
>            Reporter: Siddharth Sunil Boobna
>            Assignee: Siddharth Sunil Boobna
>            Priority: Minor
>
> Bookie Shell should have a sanity test to identify any problems with the 
> local bookie that is still registered in ZK.
> Solution:
> Add a sanity test to the bookie shell that will create a ledger locally, 
> write/read few entries and delete the ledger. To test only the local bookie, 
> the ledger ensemble size will be 1 and we implement a 
> LocalBookieEnsemblePlacementPolicy.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to