You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2017/10/06 08:45:01 UTC

[jira] [Updated] (BOOKKEEPER-1029) BookieDecommision Workflow

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

Ivan Kelly updated BOOKKEEPER-1029:
-----------------------------------
    Labels: iktriage0  (was: )

> BookieDecommision Workflow
> --------------------------
>
>                 Key: BOOKKEEPER-1029
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-1029
>             Project: Bookkeeper
>          Issue Type: New Feature
>            Reporter: Charan Reddy Guttapalem
>            Assignee: Charan Reddy Guttapalem
>              Labels: iktriage0
>
> - LostBookieRecoveryDelay config param is stored in ZK
>     - if LostBookieRecoveryDelay is reset to same value then it force triggers audit immediately
>     - Added logic to trigger immediately or schedule pending audittask depending on the changed value in ZK
>     - good number of testcases validating focetrigger/reschedluing audittask
>     - added bookieshell command to get/set LostBookieRecoveryDelay from ZK
>     - added bookieshell command to triggeraudit by resetting LostBookieRecoveryDelay
>     - added decommissionbookie bkshell command, which validates the complete replication of ledgers stored in the bookie



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)