commit | 1b2138fd4ecdbc4dfec00709b51e1367dfd49654 | [log] [tgz] |
---|---|---|
author | Pasha Kuznetsov <pasha@tydbits.com> | Thu Dec 13 17:45:11 2018 -0800 |
committer | Sijie Guo <guosijie@gmail.com> | Fri Dec 14 09:45:11 2018 +0800 |
tree | a4e96075145c22867f2adec2f5d0e34ee815391b | |
parent | 616d4c15bf85fcbe3fdfa039c8da875cc94e81f7 [diff] |
Issue #1884: (@W-5697664@) dir_*_usage stats are reported as 0 ... for read-only bookies after a restart ### Motivation Fixing the Issue #1884: When a read-only bookie is restarted it keeps reporting `dir_*_usage` stats as `0` until it becomes writable again. This is caused by the `LedgerDirsMonitor.check` only updating `diskUsages` if there are any writable dirs, or if the total usage goes below the low water mark, otherwise relying on previously filled values which are `0` after a bookie is restarted. ### Changes * Change the `LedgerDirsMonitor.check` to update `diskUsages` even when there are no writable dirs. * Add new `testLedgerDirsMonitorStartReadOnly` testing this scenario. * Simplify previous tests checking read-only since `diskUsages` are now updated regardless if a bookie is in read-only mode. jvrao reddycharan Reviewers: Sijie Guo <sijie@apache.org>, Charan Reddy Guttapalem <reddycharan18@gmail.com> This closes #1885 from pasha-kuznetsov/issue-1884-dir-usage-ro-restart, closes #1884
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.