ISSUE #2224: Config ServerConfiguration with setAllowLoopback(true) for Unit Tests

### Motivation

Unit test fails when build master branch

### Changes

Config ServerConfiguration with setAllowLoopback(true) in the class GarbageCollectorThreadTest

Master Issue: #2224 


Reviewers: Jia Zhai <zhaijia@apache.org>, Enrico Olivelli <eolivelli@gmail.com>

This closes #2226 from coolbeevip/ISSUE-2224, closes #2224 and squashes the following commits:

fdba4fbce [Lei Zhang] ISSUE-2224 set allowLoopback is true
2ff7ca5af [Enrico Olivelli] Account Apache Thrift and Http Client files in LICENSE files - Fix build on Travis
2bbf58e01 [Dapeng] Fixed bin/bookkeeper shell readjournal
9d61fb4fe [Dapeng] [DOCS] Modify “Using Autoecovery”,recover does not support the specified target bookie
2ca4025e4 [Anup Ghatage] [DOCUMENTATION] Add doc for decommissioning bookie process
62e3b9b6f [Enrico Olivelli] Make 4.9.2 as stable
40f349ccf [Enrico Olivelli] Bump Python client version
b1991e6b3 [Enrico Olivelli] Release notes for 4.10
9f4b1359e [冉小龙] Fix the log level of not support Sse42Crc32C
557dfe90f [Jennifer Huang] [DOCS] Update coding_guide.md
43f8cd74f [Enrico Olivelli] Add -Dtwitter to fix auto-build
f57962bcc [Matteo Merli] Removed mutex contention on BufferedChannel
f5d2e5931 [Enrico Olivelli] Add -Dtwitter to release scripts in order to build Twitter stats providers
7efa8e89e [Enrico Olivelli] Fix version in modules that are not active by default
d49b46f4e [Enrico Olivelli] [maven-release-plugin] prepare for next development iteration
5a4213bb0 [Enrico Olivelli] [maven-release-plugin] prepare branch branch-4.10
f8a5974a5 [Charan Reddy Guttapalem] Fix firstStoredEntryId logic in LedgerFragment
8559126a3 [Anup Ghatage] Issue #2145: Make ledgerDirs in Cookie consistent across generating a…
1 file changed
tree: 352f9a91892ef24b1d211041e9f348932d561fb7
  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.