Backend Development 7 min read

Highlights of Apache Pulsar 2.10.0 Release: New Features and Bug Fixes

The Apache Pulsar 2.10.0 release introduces automatic cluster failover, lazy‑loading producers, new TableView support, enhanced broker interceptors, enriched client authentication, Etcd metadata storage, and numerous bug fixes, offering developers and operators a more flexible and performant messaging platform.

Laravel Tech Community
Laravel Tech Community
Laravel Tech Community
Highlights of Apache Pulsar 2.10.0 Release: New Features and Bug Fixes

Apache Pulsar 2.10.0 has been released, incorporating contributions from 99 developers, over 800 changes, and a range of new features beyond the previously introduced ZooKeeper reduction and automated cluster failover.

Version Highlights include automatic failover between primary and backup clusters (PR‑13316), lazy loading for PartitionedProducer to reduce broker memory usage (PR‑10279), and a new TableView type for topic mapping based on message keys (PR‑12838).

Bug Fixes and Enhancements are grouped by component. The Java client now supports cluster‑level automatic failover, cross‑cluster topic policies, and a replicateTo attribute for local policies. Producers gain delayed loading for partitioned producers and a new ChunkMessage‑ID type with helper methods getFirstChunkMessageId and getLastChunkMessageID . Brokers receive an extended BrokerInterceptor interface and a new MessagePayloadProcessor for ledger read/write interception.

Consumers see epoch‑based redelivery synchronization, an entry‑filter framework, dead‑letter subscription initialization, and redelivery back‑off strategies for ack timeouts, including additions to RedeliveryBackoff and NegativeAckBackoff . Function enhancements introduce a RichFunction interface with setup and tearDown APIs, and asynchronous authentication methods such as AuthenticationProvider#authenticateAsync and AuthenticationProvider#authenticateHttpRequestAsync .

Topic improvements add metadata support with new storage methods and REST API paths. Metadata storage now includes an Etcd implementation offering batch reads/writes, session watches, and lease management.

Overall, the release provides significant operational, performance, and developer‑experience enhancements for Pulsar users.

metadataMessagingBrokerApache PulsarFailoverClientRelease Notes
Laravel Tech Community
Written by

Laravel Tech Community

Specializing in Laravel development, we continuously publish fresh content and grow alongside the elegant, stable Laravel framework.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.