🔒 Public CA clientAuth EKU sunset — heads up for mTLS users TL;DR: Public CAs are removing clientAuth from TLS leaf certs (rolling out now through 2027). Pulsar deployments using public-CA-issued client certs for mTLS — most notably geo-replication brokers and external producers/consumers — will fail at the next cert renewal under the new policy. Server-only TLS is unaffected. Private PKI (OpenBao, step-ca, Vault, EJBCA, optionally fronted by cert-manager) is the path forward. Full write-up on users@ mailing list: https://lists.apache.org/thread/kbtnz7srvcsg0opj0vo15qm6rcx4btf8 ASF advisory: https://news.apache.org/foundation/entry/the-public-ca-clientauth-eku-sunset-what-apache-software-deployers-need-to-know

📣 pulsarlogo [ANNOUNCE] Apache Pulsar Helm Chart version 4.6.0 Released pulsarlogo 📣 NOTICE: This release splits the ZooKeeper and Broker Kubernetes Services into separate ClusterIP and headless Services. Upgrading from pre-4.6.0 requires StatefulSet re-creation and a brief service disruption is possible. GitOps users (ArgoCD, Flux, Pulumi) should pay special attention. Testing the upgrade in a staging environment is recommended. Please check the release notes for full details before upgrading. --------------- Dear community, The Apache Pulsar team is pleased to announce the release of the Apache Pulsar Helm Chart 4.6.0. The official source release, as well as the binary Helm Chart release, are available at https://www.apache.org/dyn/closer.lua/pulsar/helm-chart/4.6.0/?action=download The helm chart index at https://pulsar.apache.org/charts/ has been updated and the release is also available directly via helm. Release Notes: https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-4.6.0 Docs: https://github.com/apache/pulsar-helm-chart#readme and https://pulsar.apache.org/docs/helm-overview ArtifactHub: https://artifacthub.io/packages/helm/apache/pulsar/4.6.0 Thanks to all the contributors who made this possible. Regards, The Apache Pulsar Team

This message was deleted.

According to https://pulsar.apache.org/contribute/release-policy/#supported-versions @Lari Hotari Hi Lari, is 3.0.17 the final release of the 3.0 LTS version? Is there a chance to extend the support period of the 3.0 LTS version branch?

Hello! I am experimenting with auto cluster failover and have it configured in my Pulsar client code that I am using to test with 2 Kubernetes clusters. From what we can tell, it is working. Although, we would like to be able to verify this in the logs - especially for when we bring cluster1 back up after failing, we'd like to know that our producer and consumer actually switched back. I've been looking deep into the broker pod logs but can't find anything verifying the failover or switch back. Is there a way we can verify?

Hi, we are using the Pulsar version 4.0.10 and would like to stay on the LTS Versions. Do you have any specific plans to release version 5.0.x? I am asking as customers are interested in potentially leveraging SMT functionality for unwrapping messages when using CDC. There is support for that in 4.1.x but as we would like to stay on the LTS Versions the question is when 5.0.x would be released.

Hello, I noticed there was an intention to release a new version of the Flink connector for Pulsar (v4.2.0): https://lists.apache.org/thread/bwd91nbcyflbhvhrm33qg7tjksl6b03w However, no binding votes were cast to approve or reject the request — only non-binding votes were submitted. What would be the next steps here? Thanks!

Hi, I'm stuck because I don't understand how to consume DLQ message (or creation of DLQ topic). I ran pulsar with this command :

docker run -it -p 6650:6650 -p 8080:8080 -e TZ=Europe/Paris --mount source=pulsardata,target=/pulsar/data --mount source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:3.0.17 bin/pulsar standalone --advertised-address localhost

Then I have these 3 java files, I run SimpleConsumerWithRetry, and gets logs :

>> pulsar client created
>> pulsar DLQ consumer created
>> pulsar consumer created

Then I run SimpleProducer, here the logs

>> pulsar client created
>> pulsar producer created
deliver msg 9:1:-1, value:Message de 2026-05-28T19:00:43.731+02

Then I look at the log of SimpleConsumerWithRetry :

2026-05-28T19:00:43.798+02: receive msg 9:1:-1, value:Message de 2026-05-28T19:00:43.731+02
2026-05-28T19:00:45.902+02: receive msg 18:0:-1, value:Message de 2026-05-28T19:00:43.731+02
2026-05-28T19:00:48.899+02: receive msg 18:1:-1, value:Message de 2026-05-28T19:00:43.731+02

So far so good : 2 retries, with 2 seconds delay. But the message is not send to the DLQ (at least, not the DLQ topic I'm listening). If I ask the topic list

curl --silent -XGET <http://localhost:8080/admin/v2/persistent/public/testns>

there is only 2 topics (I was expected 3 : main, retry, dlq) :

["<persistent://public/testns/test>","<persistent://public/testns/test-subs-DLQ>"]

. I tried also to not listen to test-subs-DLQ (removing one consumer in the code) and there is only 1 topic created (test). Any clue ?

Hi everyone, I noticed something unusual with

reconsumeLater

. When I set

delayTime

to around 1 second (or less), the message is redelivered immediately. I wrote a small integration test to reproduce this behavior (the test requires a valid Docker installation to start a Pulsar container). When running the

TestReconsumeLater.java

test, if the constant

REDELIVER_DELAY

is set to less than 1010 ms, the test fails because the message is redelivered in 34 ms instead of the expected delay:

java.lang.AssertionError:
Expected actual:
  34L
to be greater than or equal to:
  1009L

Is this a known limitation ? Is it documented anywhere ?

https://www.linkedin.com/feed/update/urn:li:activity:7468563396825780225/

In this work, we introduce Nexus, a transparent data management layer that sits between event streaming systems (e.g., Kafka, Pulsar, Pravega) and external storage (e.g., object stores). Nexus intercepts tiered storage operations and runs in-line programmable functions on chunks of stream data across the edge-cloud. This enables things like high data compression without impacting the hot path, semantic routing or labeling of stream data using AI, or caching/buffering stream data close to the edge. The policy-based,  programmable nature of the system allows for exploring many other potential use cases.

any one head about this ?

📣 pulsarlogo [ANNOUNCE] Apache Pulsar 4.0.11 released pulsarlogo 📣 The Apache Pulsar team is proud to announce Apache Pulsar version 4.0.11. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: https://pulsar.apache.org/download Release Notes are at: https://pulsar.apache.org/release-notes/versioned/pulsar-4.0.11/ We would like to thank the contributors that made the release possible. Regards, The Pulsar Team Please also check https://pulsar.apache.org/release-notes/versioned/pulsar-4.0.10 upgrade notice if you are upgrading from <4.0.10

📣 pulsarlogo [ANNOUNCE] Apache Pulsar 4.2.2 released pulsarlogo 📣 The Apache Pulsar team is proud to announce Apache Pulsar version 4.2.2. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: https://pulsar.apache.org/download Release Notes are at: https://pulsar.apache.org/release-notes/versioned/pulsar-4.2.2/ We would like to thank the contributors that made the release possible. Regards, The Pulsar Team

Pulsar 5.0.0-M1 is on it's way: https://apache-pulsar.slack.com/archives/C5ZSVEN4E/p1781266188598769

hi! When I have replicated subs enabled with geo-replication and auto cluster failover between two clusters, as messages are being sent and consumed the msgInCounter topic stat is always 4x the amount of msgOutCounter. msgOutCounter always equals the actual number of messages sent. Just wondering why msgIn is always so high compared to msgOut with with rep subs? Thanks!

We've just released Apache Pulsar Helm Chart 4.6.1 🎉 The official source release, as well as the binary Helm Chart release, are available at https://www.apache.org/dyn/closer.lua/pulsar/helm-chart/4.6.1/?action=download The helm chart index at https://pulsar.apache.org/charts/ has been updated and the release is also available directly via helm. Release Notes: https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-4.6.1 Docs: https://github.com/apache/pulsar-helm-chart#readme and https://pulsar.apache.org/docs/helm-overview ArtifactHub: https://artifacthub.io/packages/helm/apache/pulsar/4.6.1 Thanks to all the contributors who made this possible.

🎉 <!channel> Apache Pulsar 5.0.0-M1 is out! This is a milestone preview of the upcoming Pulsar 5.0 LTS, released early to gather feedback. ⚠️ Not for production — breaking changes may still land before the final 5.0 LTS. What's new in 5.0, previewed here: 🔄 Scalable Topics — a new

topic://

topic type that sizes itself to its load. The broker splits hot key-range segments and merges cold ones at runtime, no downtime, no broken per-key ordering, and no partition count to pick up front. ✨ New V5 Java client (

pulsar-client-v5

) — a clean-slate redesign with three purpose-built consumers (Stream, Queue, Checkpoint). Works with your existing topics, a consumer can subscribe to a whole namespace, and it's the only way to use Scalable Topics. The classic client API stays fully supported. 🛢️ Oxia is now the recommended metadata store for new clusters, with live zero-downtime migration from ZooKeeper. ZooKeeper is still fully supported; the etcd backend is removed in 5.0. Also notable: structured (slog-style) logging, IO connectors in a dedicated repo, the

javax.*

→

jakarta.*

migration, and a move from Maven to Gradle. 📚 Full announcement: https://pulsar.apache.org/blog/2026/06/23/announcing-apache-pulsar-5-0-m1/ ⬇️ Download: https://pulsar.apache.org/download 📝 Release notes: https://pulsar.apache.org/release-notes/versioned/pulsar-5.0.0-M1/ Thanks to everyone who made this release possible! pulsarlogo

Pulsar go client from the stream native repo support for the AVRO and JSON message schema .

📣 pulsarlogo [ANNOUNCE] Apache Pulsar 4.0.12 released pulsarlogo 📣 The Apache Pulsar team is proud to announce Apache Pulsar version 4.0.12. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: pulsar.apache.org/download Release Notes are at: pulsar.apache.org/release-notes/versioned/pulsar-4.0.12 We would like to thank the contributors that made the release possible. Regards, The Pulsar Team

📣 pulsarlogo [ANNOUNCE] Apache Pulsar 4.2.3 released pulsarlogo 📣 The Apache Pulsar team is proud to announce Apache Pulsar version 4.2.3. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: pulsar.apache.org/download Release Notes are at: pulsar.apache.org/release-notes/versioned/pulsar-4.2.3 We would like to thank the contributors that made the release possible. Regards, The Pulsar Team

Hi Everyone 👋 , got a question around the apache pulsar helm chart. I noticed the

master

version is now supporting

components.function_worker

(separate functions component instead of embedded functions in the broker). However this has not been published in the latest release 4.6.1 version yet. Are there any plans to release it please? Thanks

We've just released Apache Pulsar Helm Chart 4.7.0 🎉 The official source release, as well as the binary Helm Chart release, are available at apache.org/dyn/closer.lua/…/4.7.0?action=download The helm chart index at pulsar.apache.org/charts has been updated and the release is also available directly via helm. Release Notes: github.com/apache/…/pulsar-4.7.0 Docs: github.com/apache/pulsar-helm-chart#… and pulsar.apache.org/docs/helm-overview ArtifactHub: artifacthub.io/packages/…/4.7.0 Thanks to all the contributors who made this possible.

hi ,In the java pulsar admin we have the resetcursor with exclude the last message id ,is same approach is available in pulsar admin go ? public ResetCursorData(long ledgerId, long entryId, boolean isExcluded) { this.ledgerId = ledgerId; this.entryId = entryId; this.isExcluded = isExcluded; } func (s *subscriptions) ResetCursorToMessageID(topic utils.TopicName, sName string, id utils.MessageID) error { return s.ResetCursorToMessageIDWithContext(context.Background(), topic, sName, id) }

Do you have an Apache Pulsar use case you'd like to share with a wider audience? The final CFP deadline for Data Streaming Summit 2026 - The Data Streaming + Agent Infra Conference is in about 32 hours from now. Please submit your proposals now.

📣 pulsarlogo [ANNOUNCE] Apache Pulsar 4.0.13 released pulsarlogo📣 The Apache Pulsar team is proud to announce Apache Pulsar version 4.0.13. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: pulsar.apache.org/download Release Notes are at: pulsar.apache.org/release-notes/versioned/pulsar-4.0.13/ We would like to thank the contributors that made the release possible. Regards, The Pulsar Team

📣 pulsarlogo [ANNOUNCE] Apache Pulsar 4.2.4 released pulsarlogo📣 The Apache Pulsar team is proud to announce Apache Pulsar version 4.2.4. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management for subscribers, and cross-datacenter replication. For Pulsar release details and downloads, visit: pulsar.apache.org/download Release Notes are at: pulsar.apache.org/release-notes/versioned/pulsar-4.2.4/ We would like to thank the contributors that made the release possible. Regards, The Pulsar Team

Hi, has anyone encountered a transaction pending-ack replay thread getting stuck indefinitely? On Pulsar 4.0.10, I observed a pulsar-transaction-executor-N-1 thread stuck in MLPendingAckStore$PendingAckReplay.run(), repeatedly calling Thread.sleep(1). Because these executors are single-threaded and shared by multiple subscriptions, one stuck replay can prevent consumers from being created on unrelated subscriptions. I also observed broker pod restarts around the same time. I suspect the stuck replay may block the health-check subscription when it hashes to the affected executor, causing Kubernetes health checks to fail and restart the broker pod. My current theory is: - A managed-ledger read is issued, but its callback never arrives. - outstandingReadsRequests remains 1, the entry queue stays empty, and isReadable remains true. - PendingAckReplay therefore loops forever. - Normally, ManagedLedgerImpl.checkReadTimeout() should terminate the read, but this protection is disabled when managedLedgerReadEntryTimeoutSeconds=0. - A possible trigger is an empty or newly rolled-over pending-ack ledger being deleted while replay is reading it, because new ledgers initially have timestamp=0 and system ledgers use retention 0. I found related issues #14852, #23506, and #24401, but none appears to fully address pending-ack replay when the read callback never returns. Has anyone seen this behavior? Does this analysis seem plausible? Could this explain the broker pod restarts, and is there a recommended configuration to avoid it besides setting managedLedgerReadEntryTimeoutSeconds to a non-zero value? I have a repeatable local reproduction and thread dumps that I’m happy to share.

Hi everyone! I am launching a single node Pulsar cluster via docker-compose and following documentation for setting the yaml file up. I would like to create a pre-configured sink and pre-configured tenants/ns/topics. I am doing this just by creatinga. script that has the pulsar-cli commands to do those operations. I would like those resources to be available to the user on broker start up. My question is, where would it be best to pass in this script? as an entrypoint in the broker container? or the pulsar-init container?

another question regarding schemas .. we are streaming apache arrow record batch tables. Currently, we have to serialize the record batch into bytes, producer sends arrow bytes to consumer, consumer receives and acks, and then we have to deserialize it. Is there any ability to natively send arrow record batches without serialization.

@RunLLM If the message size is configured to maxMessageSize=5242880 in broker.conf what is the max entry size in bookie .