Google Git
Sign in
apache / bookkeeper / f62a81dda4f1f782a3fc50067bbdffd5b6f438df
commitf62a81dda4f1f782a3fc50067bbdffd5b6f438df[log] [tgz]
authorZhangJian He <shoothzj@gmail.com>Sat Apr 20 08:13:58 2024 +0800
committerGitHub <noreply@github.com>Sat Apr 20 08:13:58 2024 +0800
tree4ebd03ec9c9de286b4f07174b6082b4cdc29012c
parent2b25f45e083ae8c925b06498e02dabaf3f36eaee [diff]
improve: change scheduleAtFixedRate to scheduleWithFixedDelay in GarbageCollectorThread (#4296)

### Motivation

Current scheduling mechanism for garbage collection uses scheduleAtFixedRate. This approach schedules the next execution without considering whether the current task has finished, potentially leading to overlapping executions if a task takes longer than expected.

In my test environment, After task accumulation in gc thread pool, sometimes there is no entrylog to extract and no entrylogger to compact. But every round of gc, still need to compare ledger meta between local and metadata store (zk), which will result in highly frequently access to metadata store and each access will bring considerable unnecessary data flow.

See https://lists.apache.org/thread/023vkc5rwyq0j776zcv8dtp7c8cml6vp

Signed-off-by: ZhangJian He <shoothzj@gmail.com>
2 files changed
tree: 4ebd03ec9c9de286b4f07174b6082b4cdc29012c
  1. .github/
  2. .idea/
  3. .test-infra/
  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-slogger/
  13. buildtools/
  14. circe-checksum/
  15. conf/
  16. cpu-affinity/
  17. deploy/
  18. dev/
  19. docker/
  20. metadata-drivers/
  21. microbenchmarks/
  22. native-io/
  23. shaded/
  24. site3/
  25. src/
  26. stats/
  27. stream/
  28. tests/
  29. testtools/
  30. tools/
  31. .asf.yaml
  32. .dlc.json
  33. .gitignore
  34. CONTRIBUTING.md
  35. LICENSE
  36. NOTICE
  37. pom.xml
  38. README.md
README.md

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, Pravega.
  • Message Store, e.g. Apache Pulsar.
  • Offset/Cursor Store, e.g. Apache Pulsar.
  • Object/Blob Store, e.g. storing state machine snapshots.

Get Started

  • Checkout the project website.
  • Concepts: Start with the basic concepts of Apache BookKeeper. This will help you to fully understand the other parts of the documentation.
  • Follow the Installation guide to set up BookKeeper.

Documentation

Please visit the Documentation from the project website for more information.

Get In Touch

Report a Bug

For filing bugs, suggesting improvements, or requesting new features, help us out by opening a GitHub issue.

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 our installation guide to get your local environment setup.

  2. Take a look at our open issues: GitHub Issues.

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

  4. Make your changes according to our contributing guide