Google Git
Sign in
apache / bookkeeper / 7ad5849b1b0d9dbf2274a6fd00ad26f7286f7cff
commit7ad5849b1b0d9dbf2274a6fd00ad26f7286f7cff[log] [tgz]
authorYong Zhang <zhangyong1025.zy@gmail.com>Tue Apr 09 20:00:26 2019 +0800
committerSijie Guo <guosijie@gmail.com>Tue Apr 09 20:00:26 2019 +0800
tree3953b2c86c14300ce7f19116fdbd2caad4e06042
parentd4dbb6bfb6cd7a56a8baf95472a7f6fc680d0ca2 [diff]
Migrate command `regenerate-interleaved-storage-index-file`

Descriptions of the changes in this PR:

#2033 

```
Regenerate an interleaved storage index file, from available entrylogger files.

Usage:  bkctl bookie regenerate-interleaved-storage-index-file [flags]

Flags:

    -b, --b64password
        The password in base64 encoding, for cases where the password is not
        UTF-8.

    -d, --dryrun
        Process the entryLogger, but don't write anthing.

    -l, --ledgerids
        Ledger(s) whose index needs to be regenerated. Multiple can be
        specified, comma separated.

    -p, --password
        The bookie stores the password in the index file, so we need it to
        regenerate.This must match the value in the ledger metadata.


    -h, --help
        Display help information
```


Reviewers: Sijie Guo <sijie@apache.org>

This closes #2035 from zymap/command-RISIF
4 files changed
tree: 3953b2c86c14300ce7f19116fdbd2caad4e06042
  1. .github/
  2. .test-infra/
  3. .travis_scripts/
  4. bin/
  5. bookkeeper-benchmark/
  6. bookkeeper-common/
  7. bookkeeper-common-allocator/
  8. bookkeeper-dist/
  9. bookkeeper-http/
  10. bookkeeper-proto/
  11. bookkeeper-server/
  12. bookkeeper-stats/
  13. bookkeeper-stats-providers/
  14. buildtools/
  15. circe-checksum/
  16. conf/
  17. cpu-affinity/
  18. deploy/
  19. dev/
  20. docker/
  21. metadata-drivers/
  22. microbenchmarks/
  23. shaded/
  24. site/
  25. stats/
  26. stream/
  27. tests/
  28. tools/
  29. .gitignore
  30. .travis.yml
  31. LICENSE
  32. NOTICE
  33. pom.xml
  34. README.md
README.md

Build Status Build Status Coverage Status Maven Central

Apache BookKeeper

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:

  • WAL (Write-Ahead-Logging), e.g. HDFS NameNode.
  • Message Store, e.g. Apache Pulsar.
  • Offset/Cursor Store, e.g. Apache Pulsar.
  • Object/Blob Store, e.g. storing state machine snapshots.

Get Started

  • Concepts: Start with the basic concepts of Apache BookKeeper. This will help you to fully understand the other parts of the documentation.
  • Getting Started to setup BookKeeper to write logs.

Documentation

Developers

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.

Administrators

Contributors

Get In Touch

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.

Need Help?

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.

Contributing

We feel that a welcoming open community is important and welcome contributions.

Contributing Code

  1. See Developer Setup to get your local environment setup.

  2. Take a look at our open issues: JIRA Issues Github Issues.

  3. Review our coding style and follow our pull requests to learn about our conventions.

  4. Make your changes according to our contribution guide.

Improving Website and Documentation

  1. See Building the website and documentation on how to build the website and documentation.