commit | e7430ce25e3609bf77b028e4f0475dad2147c22d | [log] [tgz] |
---|---|---|
author | Rajan Dhabalia <rdhabalia@apache.org> | Tue Mar 31 12:12:16 2020 -0700 |
committer | GitHub <noreply@github.com> | Tue Mar 31 12:12:16 2020 -0700 |
tree | a12f08307d67bc006234857817180e141b8ee0b1 | |
parent | 665565e9802c3aec4b49df5dd53967b6d1981ca6 [diff] |
[bookie-server-config] Avoid considering empty journalDirectories As discussed at : https://github.com/apache/pulsar/issues/6042 ### Issue We have config management tool which manages bookie-server configuration and sets empty value of `journalDirectories` if bookie-server is still wants to use single journal dir: `journalDirectory`. In this case, bookie-server doesn't consider `journalDirectory` value and keeps empty list of `journalDirectories` which stats bookie with invalid configuration. ### Expected behavior Bookie-server should parse empty configuration `journalDirectories=` properly and avoid picking up empty value of `journalDirectories` and in that case, bookie-server should fallback to `journalDirectory` config. Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <None> This closes #2245 from rdhabalia/journal_dir
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.