commit | dcb2b95f50ad8177d9fb4a1c9b5c72b8be70aa1e | [log] [tgz] |
---|---|---|
author | Yang Yang <yyang@streamnative.io> | Thu Jun 24 11:46:09 2021 +0800 |
committer | GitHub <noreply@github.com> | Wed Jun 23 20:46:09 2021 -0700 |
tree | 69979b82a8837381527d78ae10b90fe0f7bed6ec | |
parent | ac76a0867658ba87bb5a56b7bcd5655fc4d73096 [diff] |
Print usage in autorecovery command if needed (#2743) ### Motivation I was trying to read the code to see how auto-recovery service works, just noticed the method `printUsage` was never called and the program doesn't print the usage even when '-h' is specified. ### Changes Print the usage of auto-recovery if '-h' is specified or additional unexpected arguments are provided when running the auto-recovery command.
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 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.