commit | 08209f47495c75c6acfbdd96691557d581943a25 | [log] [tgz] |
---|---|---|
author | lamber-ken <lamberken@apache.org> | Sat May 30 08:39:58 2020 +0800 |
committer | GitHub <noreply@github.com> | Fri May 29 17:39:58 2020 -0700 |
tree | 8a6cd9534aa71882741ff7ce0a78480ab2898f34 | |
parent | 52330277565021c9d30d268cefee3e2bad1db5ae [diff] |
[LOG] Change ERROR to INFO log level ### Motivation When use shell command, it output nothing caused by `ERROR` level. **OLD** (output nothing) ``` bin/bookkeeper shell readlogmetadata 0 ``` **FIX** ``` bin/bookkeeper shell readlogmetadata 0 06:58:01,364 INFO Print entryLogMetadata of entrylog 0 (0.log) 06:58:01,467 INFO Failed to get ledgers map index from: 0.log : No ledgers map index found on entryLogId0 06:58:01,471 INFO --------- Lid=0, TotalSizeOfEntriesOfLedger=59 --------- ``` ### Changes - Remove duplicate definition `VERBOSECONSOLE ` - Change `ERROR` to `INFO` Reviewers: Sijie Guo <None> This closes #2350 from lamber-ken/bk-improve-shell-log-level
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.