commit | 54ce17312f53c9b2a1ac3ea83303a7bebebc0a31 | [log] [tgz] |
---|---|---|
author | Hugo Abreu <6619758+hugomiguelabreu@users.noreply.github.com> | Fri Jun 21 04:22:33 2019 +0100 |
committer | Sijie Guo <guosijie@gmail.com> | Thu Jun 20 20:22:33 2019 -0700 |
tree | 2ea9ab1ceff6c4e2715ba24429cfdb5f45e5484f | |
parent | 96fc2e2aac4d026fe336ae8347521d9910165dd5 [diff] |
Added zookeeper host configuration. Closes #1960 Descriptions of the changes in this PR: Added host IP binding to sandbox. ### Motivation Allowing running the sandbox inside guest machines and be accessible by all system (including other guest machines). When binding 127.0.0.1 other guest machines will experience an error. By allowing to bind the correct IP the namespace will be available and correctly configured for other hosts. ### Changes Added a new argument to the _dlog_ tool allowing to define the host IP to bind ZooKeeper and DistributedLog namespace. Master Issue: #1960 Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2081 from hugomiguelabreu/master, closes #1960
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.