This is the seventh release of BookKeeper as an Apache Top Level Project!
The 4.6.0 release incorporates new fixes, improvements, and features since previous major release 4.5.0.
Apache BookKeeper users are encouraged to upgrade to 4.6.0. The technical details of this release are summarized below.
The main features in 4.6.0 cover are around following areas:
- Dependencies Upgrade
- Bookie enhancement
- BookKeeper Admin REST API
- New BookKeeper API
- Performance improvement
- Deployment or Ease of use
- Upgrade Protobuf to
- Persistable bookie status.
- Prior to this release, bookie status was transient. It is a bit hard for management tooling. This feature adds persistable bookies status. See Issue-265 for more details.
- Introduce Bookie Discovery Interface. Prior to this release, bookkeeper client only provides interfaces for ledger metadata management. It doesn’t provide any interface for service discovery part. This feature introduces bookie discovery interface, so it allows plugging in different service discovery backends for bookkeeper.
- Lifecycle components for managing components in bookie server.
- Make bookie recovery work with recovering multiple bookies.
- Make recovery tool work with multiple bookies, so that one call could recover multiple bookies. See Issue-612 for more details.
BookKeeper Admin REST API
- Introduce a bookkeeper admin endpoint for operations to interact and administer the bookkeeper cluster using REST API. see PR-278, Issue-520, and Issue-674 for more details.
New BookKeeper API
- New Fluent Style API.
Use ByteBuf in multiple places to avoid unnecessary memory allocation and reduce the garbage produced in JVM. See PR-640 for more details.
Separate the FileInfo cache into write and read cache. It avoids catchup reads impact tailing reads and writes. See PR-513 for more details.
Deployment or Ease of use
- Deployment BookKeeper on K8s.
Existing API changes
- BookKeeper constructor now throws BKException instead of KeeperException.
- The signatures of
reorderReadLACSequenceare changed in EnsemblePlacementPolicy.