commit | e25c5487aeb4797bc4f86753428c4b5c319a4b25 | [log] [tgz] |
---|---|---|
author | 赤月 <974226358@qq.com> | Wed Feb 21 10:53:40 2024 +0800 |
committer | GitHub <noreply@github.com> | Wed Feb 21 10:53:40 2024 +0800 |
tree | f4cd1b67b4bc9c1522c38ac354faceb0a4f04079 | |
parent | eb27e6ed3ccd1ee46f372ae6fd0a53ccea81908f [diff] |
[improve] fix doc & fix listfilesondisc cmd description (#4184) Descriptions of the changes in this PR: ## Journal settings | Parameter | Description | Default | --------- | ----------- | ------- | | journalDirectories | The directories to which Bookkeeper outputs its write-ahead log (WAL). Could define multi directories to store write head logs, separated by ','.<br />For example:<br /> journalDirectories=/tmp/bk-journal1,/tmp/bk-journal2<br />If journalDirectories is set, bookies will skip journalDirectory and use this setting directory.<br /> | /tmp/bk-journal | | journalDirectory | @Deprecated since 4.5.0, in favor of using `journalDirectories`.<br /><br />The directory to which Bookkeeper outputs its write-ahead log (WAL).<br /> | /tmp/bk-txn | ### Motivation update doc about conf#JournalDirectory 2 conf#JournalDirectories& fix listfilesondisc cmd description ### Changes Master Issue: #4183
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:
Please visit the Documentation from the project website for more information.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a GitHub issue.
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 our installation guide to get your local environment setup.
Take a look at our open issues: GitHub Issues.
Review our coding style and follow our pull requests to learn more about our conventions.
Make your changes according to our contributing guide