Sunday Live｜Analysis of new features of Apache Pulsar 2.10.0

About TGIP

TGIP is the abbreviation of Thank God It's Pulsar, inspired by the Google team's Thank God It's Friday, indicating that the work week is coming to an end, and there will be another happy weekend soon. TGIP is mainly to introduce some basic concepts about Pulsar to everyone, whether it is its architectural model, or the transmission dynamics between messages, etc., you can get it from the live broadcast of TGIP. The live broadcast of TGIP is usually scheduled on Sunday, which will not take up too much of everyone's time. Wouldn't it be nice to use the weekend to learn about Apache Pulsar?

The new issue of TGIP-CN is here! In the last issue of TGIP-CN, Zhai Jia brought you an introduction to Apache Pulsar technology progress and community dynamics in 2022. I believe that many small partners have a basic understanding of the overall technology progress and community dynamic planning.

In the technical progress of the last issue of TGIP-CN, the most eye-catching version is Apache Pulsar 2.10.0. 2.10.0 contains 1000 commits from 99 contributors, introduces up to 300 important updates, new feature support and stability enhancements, which is an unprecedented milestone for Apache Pulsar.

On March 27th, at 11:00 a.m. this Sunday, Li Penghui, a member of Apache Pulsar PMC and chief architect of StreamNative, specially brought you "Analysis of New Features of Apache Pulsar 2.10.0", shared the interpretation of the version, and answered your questions about the technology Questions about details. This new feature introduction includes the following three directions:

new features

• Remove the strong dependence on ZooKeeper;
• The introduction of TableView reduces the cost of building key-value pair views for users;
• Add a multi-cluster automatic failover strategy on the client side;
• Added message retry exponential backoff delay policy.

Pulsar Operations

• Introduce multi-cluster global topic policy setting support and topic-level cross-region replication configuration;
• Numerous topic-level policy configurations.

stability

• Modify the default ZooKeeper Session expiration policy to reconnect: ensure that the Broker will not go down when the ZooKeeper Session expires;
• Added support for batch operation Metadata service: It can improve the stability of Pulsar in scenarios with a large number of topics.

Pulsar 2.10.0 is coming soon. Want to get an early look at the exciting new features of Apache Pulsar 2.10.0? Scan the QR code of the poster below to register for this TGIP-CN now!

event information

Organizer: StreamNative

Event time: March 27 (Sunday) 11:00-12:00

Participation method: scan the code or click the link to register (after scanning the code, please add WeChat: StreamNative_bj, reply "Live" to join the live broadcast exchange group to get the review materials as soon as possible)

Related Reading

• TGIP-CN 036: Anticipate 2022 · Apache Pulsar Technology Progress and Community Dynamics
• TGlP-CN 035: Apache Pulsar Hands-on Practice Phase II: Container Deployment Practice

---

Follow the "Apache Pulsar" public account to get more technical dry goods

Join the Apache Pulsar Chinese exchange group👇🏻