Google Git
Sign in
apache / bookkeeper / 36be8362399341022c8de64f9319270726df2cb3
commit36be8362399341022c8de64f9319270726df2cb3[log] [tgz]
authorkaranmehta93 <k.mehta@salesforce.com>Fri May 17 10:38:43 2019 -0700
committerCharan Reddy Guttapalem <reddycharan18@gmail.com>Fri May 17 10:38:43 2019 -0700
tree458747a99f0664e5c56a4708dd90bf03db61a812
parent335c2aba9bfd24eff224f1afae393026c17a2d5a [diff]
Update and flush lastLogMark when replaying journal

Descriptions of the changes in this PR:

Update `lastLogMark` in memory after replaying each journal
Check for writable ledger dirs with `minUsableSizeForEntryLogCreation` to flush the `lastMark` file for bookies in ReadOnlyMode
Log line changes

### Motivation

Master Issue: #2087 


Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Charan Reddy Guttapalem <reddycharan18@gmail.com>, Sijie Guo <sijie@apache.org>, Venkateswararao Jujjuri (JV) <None>

This closes #2090 from karanmehta93/master and squashes the following commits:

f802cf6da [Karan Mehta] Fixed small issue in constuctor chaining in BookKeeperClusterTestCase
407e9f1ff [Karan Mehta] Moved lastLogMark updation logic to Journal.java
585313196 [Karan Mehta] Fix checkstyle errors
c3d47014a [Karan Mehta] Fix testJournalLogAddEntryCalledCorrectly test
c72b7b55e [Karan Mehta] Addressed nit
5d238f2b7 [Karan Mehta] Refactored code to update lastLogMark only when replaying journal and addressed nits
b5515697f [Karan Mehta] Issue #2087 Update and flush lastLogMark when replaying journal
d35aa22ad [Charan Reddy Guttapalem] Move common placementpolicy components to TopologyAwareEnsemblePlacementPolicy.
7 files changed
tree: 458747a99f0664e5c56a4708dd90bf03db61a812
  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.