commit | 06f2b6f50ca2c6c1ccc630aa9d9fd761abf1becc | [log] [tgz] |
---|---|---|
author | Yong Zhang <zhangyong1025.zy@gmail.com> | Wed Apr 10 09:42:04 2019 +0800 |
committer | Sijie Guo <guosijie@gmail.com> | Wed Apr 10 09:42:04 2019 +0800 |
tree | 7f679be3698b76b6d200a6be6b531ee7d3009722 | |
parent | 7ad5849b1b0d9dbf2274a6fd00ad26f7286f7cff [diff] |
Migrate command `updateledgers` Descriptions of the changes in this PR: #2057 ``` Update bookie id in ledgers (this may take a long time). Usage: bkctl ledger update [flags] Flags: -host, --hostname Expects configuration useHostNameAsBookieID=true as the optin value -l, --limit Maximum number of ledgers of ledgers to update (default: no limit) -p, --printprogress Print messages on every configured seconds if verbose turned on (default: 10 secs) -v, --verbose Print status of the ledger updation (default: false) -s, updatepersec Number of ledgers updating per second (default: 5 per sec) -h, --help Display help information ``` Reviewers: Jia Zhai <zhaijia@apache.org>, Sijie Guo <sijie@apache.org> This closes #2058 from zymap/command-updateledgers
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.