commit | 029e8e0e02d8e384e7d08ca548b593368574cf36 | [log] [tgz] |
---|---|---|
author | Dapeng <42792537+SunDapengcmss@users.noreply.github.com> | Sat Oct 26 11:53:32 2019 +0800 |
committer | Sijie Guo <guosijie@gmail.com> | Sat Oct 26 11:53:32 2019 +0800 |
tree | b280dd07258b89722accf1d16c9898ca09e5a1c6 | |
parent | 798a97eb14da3c00bf73eac14553ab0c06ccca14 [diff] |
[DOC] Improve the Manual deployment document. ### Motivation Following the [Manual deployment](https://bookkeeper.apache.org/docs/latest/deployment/manual/), startup bookie may have failure since there is no znode(e.g. /ledger) about bookie in zookeeper. ### Changes Modify the site/docs/latest/deployment/manual.md, set up cluster metadata before startup of bookie. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2183 from SunDapengcmss/branch-2183
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.