Google Git
Sign in
apache / bookkeeper / refs/heads/branch-4.10
commit1bf43b037c3d73072985072e8c69d504480c5adf[log] [tgz]
authorpkumar-singh <65131575+pkumar-singh@users.noreply.github.com>Tue Feb 09 03:48:13 2021 -0800
committerEnrico Olivelli <eolivelli@apache.org>Tue Feb 09 12:49:00 2021 +0100
treeefaee32afb49d0536cc857af941777ca3c6f658f
parent9f6c49b2c970e17d94cde3af38ed20bc2bbc0e97 [diff]
Fix hanging tests tests TestStorageServerClientManagerImpl

Descriptions of the changes in this PR:

**Motivation**
Fixing hanging tests TestStorageServerClientManagerImpl and other tests in the directory

Some tests were not running because they were hanging waiting on future while storage container was being fetched.
But inproc grpc server was running on endpoint fake-server while client was connecting on fake-server:4181

**Changes**
Make GRPC inproc server run on fake-server:4181 and client connect on fake-server:4181

Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Andrey Yegorov <andrey.yegorov@datastax.com>

This closes #2587 from pkumar-singh/fix_hanging_unit_tests

(cherry picked from commit 8b22a7b9d828c699a3fa62071ae4fecc62248201)
Signed-off-by: Enrico Olivelli <eolivelli@apache.org>
3 files changed
tree: efaee32afb49d0536cc857af941777ca3c6f658f
  1. .github/
  2. .test-infra/
  3. bin/
  4. bookkeeper-benchmark/
  5. bookkeeper-common/
  6. bookkeeper-common-allocator/
  7. bookkeeper-dist/
  8. bookkeeper-http/
  9. bookkeeper-proto/
  10. bookkeeper-server/
  11. bookkeeper-stats/
  12. bookkeeper-stats-providers/
  13. buildtools/
  14. circe-checksum/
  15. conf/
  16. cpu-affinity/
  17. deploy/
  18. dev/
  19. docker/
  20. metadata-drivers/
  21. microbenchmarks/
  22. shaded/
  23. site/
  24. stats/
  25. stream/
  26. tests/
  27. tools/
  28. .gitignore
  29. LICENSE
  30. NOTICE
  31. pom.xml
  32. 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.