[jira] [Closed] (BOOKKEEPER-892) Add a sanity test to help identify bookie nodes with problems that prevent writes but is still registered in ZK

["Matteo Merli (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matteo Merli closed BOOKKEEPER-892.
-----------------------------------

Closed as part of BookKeeper-4.4.0 release

> 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
>             Fix For: 4.4.0
>
>
> 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)