GitHub user reddycharan opened a pull request: https://github.com/apache/bookkeeper/pull/127
BOOKKEEPER-1028 and BOOKKEEPER-1029 BOOKKEEPER-1028: inc/excl opts listunderreplicated - Introduce including and excluding BookieId options for listunderreplicatedLedgers - But there is limitation that, since replicaslist wont be updated in underreplicatedledger zNode there is possibility of stale information --------------------------------------------------------- BOOKKEEPER-1029: BookieDecommision Workflow - 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 You can merge this pull request into a Git repository by running: $ git pull https://github.com/reddycharan/bookkeeper listunderreplicatedpredicate Alternatively you can review and apply these changes as the patch at: https://github.com/apache/bookkeeper/pull/127.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 #127 ---- commit f4787383fbf7251dd82075c5b959342b137949c7 Author: cguttapalem <cguttapa...@salesforce.com> Date: 2016-10-14T06:32:39Z BOOKKEEPER-1028: inc/excl opts listunderreplicated - Introduce including and excluding BookieId options for listunderreplicatedLedgers - But there is limitation that, since replicaslist wont be updated in underreplicatedledger zNode there is possibility of stale information commit 699cf56f4262d3a7d655bc64f00dded6bc814ee3 Author: Charan Reddy Guttapalem <cguttapa...@salesforce.com> Date: 2017-02-28T21:23:34Z BOOKKEEPER-1029: BookieDecommision Workflow - 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 ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---