Is the Algolia search on the Pulsar docs website not working for anyone else or just me? Tried with both Chrome and Firefox (with and without adblockers)

Is anyone working on Apache Flink Pulsar Connector thats compatible with Flink 1.20 or the 2.x release? Slack Conversation

Pulsar CI is broken. Please review the fix: https://github.com/apache/pulsar/pull/24155

@Lari Hotari https://github.com/apache/pulsar/pull/24097 and https://github.com/apache/pulsar/pull/24118 breaks the Pulsar CI. I submitted https://github.com/apache/pulsar/pull/24154 to fix the CI(broker-group-1).

Pulsar CI is broken again. BrokerServiceChaosTest doesn't pass. There are 2 PRs that address this issue: • https://github.com/apache/pulsar/pull/24162 • https://github.com/apache/pulsar/pull/24161 These address different problems but result in addressing the flakiness. Please review and merge to get Pulsar CI working again. /cc @Heesung Sohn @merlimat

@Lari Hotari Is there an existing plan or ongoing work to ensure that the client’s IP address is forwarded from the pulsar-proxy to the broker? Currently, when using the stats API—which returns publisher and consumer data—the reported IP address is that of the proxy, not the actual client. This makes it difficult to identify or trace the original producer or consumer.

trying to fix some flaky tests. Please review https://github.com/apache/pulsar/pull/24165

@Lari Hotari or some one else can u please help me take a look below cursor

"cursors" : {
    "15277-intentData" : {
      "markDeletePosition" : "273317793:-1",
      "readPosition" : "273976549:1",
      "waitingReadOp" : true,
      "pendingReadOps" : 0,
      "messagesConsumedCounter" : 0,
      "cursorLedger" : -1,
      "cursorLedgerLastEntry" : -1,
      "individuallyDeletedMessages" : "[]",
      "lastLedgerSwitchTimestamp" : "2025-04-03T10:51:15.71Z",
      "state" : "NoLedger",
      "active" : true,
      "numberOfEntriesSinceFirstNotAckedMessage" : 9,
      "totalNonContiguousDeletedMessagesRange" : 0,
      "subscriptionHavePendingRead" : true,
      "subscriptionHavePendingReplayRead" : false,
      "properties" : { }
    }

is it messed up ? message id on the top is 273317793 right now (based peekmessage), backlog has 8 messages but state shows noLedger.

https://lists.apache.org/thread/39t9l19zdlqocpvt55xcobhrdmt34y0o [VOTE] Release Apache Pulsar Helm Chart 4.0.1 based on 4.0.1-candidate-1 Hello Apache Pulsar Community, This is a call for the vote to release the Apache Pulsar Helm Chart version 4.0.1. Release notes for 4.0.1-candidate-1: https://github.com/apache/pulsar-helm-chart/releases/tag/pulsar-4.0.1-candidate-1 The release candidate is available at: https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/4.0.1-candidate-1/ pulsar-chart-4.0.1-source.tar.gz - is the "main source release". pulsar-4.0.1.tgz - is the binary Helm Chart release. Public keys are available at: https://www.apache.org/dist/pulsar/KEYS For convenience "index.yaml" has been uploaded (though excluded from voting), so you can also run the below commands.

helm repo add --force-update apache-pulsar-dist-dev \
<https://dist.apache.org/repos/dist/dev/pulsar/helm-chart/4.0.1-candidate-1/>
helm repo update
helm install pulsar apache-pulsar-dist-dev/pulsar \
--version 4.0.1 --set affinity.anti_affinity=false \
--wait --timeout 10m --debug

For observing the deployment progress, you can use the k9s tool to view the cluster state changes in a different terminal window. The k9s tool is available at https://k9scli.io/topics/install/. pulsar-4.0.1.tgz.prov - is also uploaded for verifying Chart Integrity, though it is not strictly required for releasing the artifact based on ASF Guidelines. You can optionally verify this file using this helm plugin https://github.com/technosophos/helm-gpg, or by using helm --verify (https://helm.sh/docs/helm/helm_verify/). helm fetch --prov apache-pulsar-dist-dev/pulsar helm plugin install https://github.com/technosophos/helm-gpg helm gpg verify pulsar-4.0.1.tgz The vote will be open for at least 72 hours. Only votes from PMC members are binding, but members of the community are encouraged to test the release and vote with "(non-binding)". For license checks, the .rat-excludes files is included, so you can run the following to verify licenses (just update ): tar -xvf pulsar-chart-4.0.1-source.tar.gz cd pulsar-chart-4.0.1 java -jar /apache-rat-0.15/apache-rat-0.15.jar . -E .rat-excludes Please note that the version number excludes the

-candidate-X

string, so it's now simply 4.0.1. This will allow us to rename the artifact without modifying the artifact checksums when we actually release it. Thanks, Lari

Please review https://github.com/apache/pulsar-client-reactive/pull/208 , it fixes pulsar-client-reactive CI.

Please review ::

pulsar-site

• PR: Updating the article page with a blog post • PR: Fix tag rendering in Card component for resource entries

Release vote started for the Reactive Java client for Apache Pulsar 0.6.0 based on 0.6.0-candidate-1: https://lists.apache.org/thread/68nws493bhhbm488kfp2wmj0lj8dxv17 Please help validate the release and vote!

Please help review this PR, thanks! https://github.com/apache/pulsar/pull/24076

Please help vote this PIP, thanks! https://lists.apache.org/thread/n86f1023d7znlz3cwr7bfpm7123njn18

Hello All, recently facing some issue with pulsar (v 4.0.0 ) client,

org.apache.pulsar.broker.service.ServerCnx - [[id: 0xd8927293, L:/<host>:6650 - R:/<host>:54788] [SR:<host>, state:Connected]] Subscribing on topic <persistent://eventhub/xux/__transaction_buffer_snapshot-partition-0> / __system_reader-multiTopicsReader-b5a83d3ad0. consumerId: 3865, role: null
2025-04-17T00:38:01.443970374Z stdout F 2025-04-16T17:38:01,443-0700 [pulsar-io-19-29] WARN  org.apache.pulsar.broker.service.ServerCnx - [/10.182.59.20:54788][<persistent://eventhub/rtngcepymt/__transaction_buffer_snapshot-partition-0][__system_reader-multiTopicsReader-b5a83d3ad0>] Failed to create consumer: consumerId=3865, Failed to load topic within timeout
2025-04-17T00:38:01.444003574Z stdout F java.util.concurrent.CompletionException: org.apache.pulsar.common.util.FutureUtil$LowOverheadTimeoutException: Failed to load topic within timeout
2025-04-17T00:38:01.444014334Z stdout F 	at java.base/java.util.concurrent.CompletableFuture.encodeRelay(Unknown Source) ~[?:?]
2025-04-17T00:38:01.444023234Z stdout F 	at java.base/java.util.concurrent.CompletableFuture.uniComposeStage(Unknown Source) ~[?:?]
2025-04-17T00:38:01.444032124Z stdout F 	at java.base/java.util.concurrent.CompletableFuture.thenCompose(Unknown Source) ~[?:?]
2025-04-17T00:38:01.444045994Z stdout F 	at org.apache.pulsar.broker.service.ServerCnx.lambda$handleSubscribe$24(ServerCnx.java:1330) ~[org.apache.pulsar-pulsar-broker-4.0.0.jar:4.0.0]
2025-04-17T00:38:01.444056064Z stdout F 	at java.base/java.util.concurrent.CompletableFuture.uniApplyNow(Unknown Source) [?:?]
2025-04-17T00:38:01.444068984Z stdout F 	at java.base/java.util.concurrent.CompletableFuture.uniApplyStage(Unknown Source) [?:?]
2025-04-17T00:38:01.444079084Z stdout F 	at java.base/java.util.concurrent.CompletableFuture.thenApply(Unknown Source) [?:?]
2025-04-17T00:38:01.444091314Z stdout F 	at org.apache.pulsar.broker.service.ServerCnx.handleSubscribe(ServerCnx.java:1271) [org.apache.pulsar-pulsar-broker-4.0.0.jar:4.0.0]
2025-04-17T00:38:01.444101514Z stdout F 	at org.apache.pulsar.common.protocol.PulsarDecoder.channelRead(PulsarDecoder.java:243) [org.apache.pulsar-pulsar-common-4.0.0.jar:4.0.0]
2025-04-17T00:38:01.444115774Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444128214Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444138334Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444150844Z stdout F 	at io.netty.handler.flow.FlowControlHandler.dequeue(FlowControlHandler.java:202) [io.netty-netty-handler-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444160774Z stdout F 	at io.netty.handler.flow.FlowControlHandler.channelRead(FlowControlHandler.java:164) [io.netty-netty-handler-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444172794Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444182814Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444195204Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444205294Z stdout F 	at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:346) [io.netty-netty-codec-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444217384Z stdout F 	at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:318) [io.netty-netty-codec-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444250454Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:444) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444261114Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444273314Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444283234Z stdout F 	at io.netty.handler.flush.FlushConsolidationHandler.channelRead(FlushConsolidationHandler.java:152) [io.netty-netty-handler-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444293274Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:442) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444305384Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444326004Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:412) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444338764Z stdout F 	at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1357) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444349094Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:440) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444361064Z stdout F 	at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:420) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444371104Z stdout F 	at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:868) [io.netty-netty-transport-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444383714Z stdout F 	at io.netty.channel.epoll.AbstractEpollStreamChannel$EpollStreamUnsafe.epollInReady(AbstractEpollStreamChannel.java:799) [io.netty-netty-transport-classes-epoll-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444393924Z stdout F 	at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:501) [io.netty-netty-transport-classes-epoll-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444406734Z stdout F 	at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:399) [io.netty-netty-transport-classes-epoll-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444419234Z stdout F 	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) [io.netty-netty-common-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444431494Z stdout F 	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) [io.netty-netty-common-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444456084Z stdout F 	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) [io.netty-netty-common-4.1.113.Final.jar:4.1.113.Final]
2025-04-17T00:38:01.444466984Z stdout F 	at java.base/java.lang.Thread.run(Unknown Source) [?:?]

based on message verified following classes service/ServerCnx.java noticed couple of comments // There was an early request to create a consumer with same consumerId. This can happen // when // client timeout is lower the broker timeouts. We need to wait until the previous // consumer // creation request either complete or fails.

Hell all, I just tried to upgrade our kubernetes pulsar cluster to 3.0.11, as usual , zookeeper and bookkeeper has no issues,

whenever upgrading broker,
```org.apache.pulsar.client.api.PulsarClientException$BrokerMetadataException: {"errorMsg":"Invalid channel state:LeaderElectionServiceStarted","reqId":4401784957004569707, "remote":"pulsar-broker-2.pulsar-broker.pulsar.svc.cluster.local/172.20.36.72:6650", "local":"/172.20.36.72:58700"}

but it will start properly if scale down to 0 and scale back ( a full restart) . this has happened to last releases from 3.0.6 , can any one shed some lights ? why rolling upgrade always got "Invalid channel state:LeaderElectionServiceStarted" ?

is there a Pulsar PMC member available to vote on the Pulsar Helm Chart release 4.0.1 ? It's been waiting for more votes for a very long time. https://lists.apache.org/thread/39t9l19zdlqocpvt55xcobhrdmt34y0o

This seems like a long shot, but any chance JClouds could be updated to a

SNAPSHOT

release? I am looking for

eu-south-1

AWS region support for S3 offloads: https://github.com/apache/jclouds/pull/219

0------

please review the fix for a flaky test: https://github.com/apache/pulsar/pull/24261 . I'll postpone merging the Mockito 5.17 upgrade until that is merged, comment https://github.com/apache/pulsar/pull/24241#issuecomment-2857124874

Please review improvements to the GitHub issue templates. It fixes some frustrations that I have had in reporting issues and reading reported issues: https://github.com/apache/pulsar/pull/24264

Pulsar CI seems to be broken by a test that consistently fails. https://github.com/apache/pulsar/issues/24262

hello all, it got error for one topic

[<persistent://0/Orchestration/AutomationExec-1017>] [AutomationJobExecEngine] Could not get connection to broker: org.apache.pulsar.client.api.PulsarClientException: {"errorMsg":"Failed to load topic within timeout","reqId":258591838108179582, "remote":"pulsar-automation-proxy.pulsar-automation.svc.cluster.local.analytics.svc.cluster.local/10.100.151.1:6650", "local":"/172.20.94.189:39002"} -- Will try again in 54.665 s

after i set maxUnackedMessagesPerConsumer to 1 for shared subscriptions other topics are fine. any reason ? it has

2025-05-07T17:10:43,725+0000 [metadata-store-11-1] INFO  org.apache.bookkeeper.client.MetadataUpdateLoop - UpdateLoop(ledgerId=5397,loopId=3df7f546) conflict writing metadata to store, update local value and try again

----- and below errors 


 bin/pulsar-admin topics stats <persistent://0/Orchestration/AutomationExec-1017>

 --- An unexpected error occurred in the server ---

Message: Failed to load topic within timeout

Stacktrace:

org.apache.pulsar.common.util.FutureUtil$LowOverheadTimeoutException: Failed to load topic within timeout
	at org.apache.pulsar.broker.service.BrokerService.futureWithDeadline(...)(Unknown Source)


Reason: 
 --- An unexpected error occurred in the server ---

Message: Failed to load topic within timeout

Stacktrace:

org.apache.pulsar.common.util.FutureUtil$LowOverheadTimeoutException: Failed to load topic within timeout
	at org.apache.pulsar.broker.service.BrokerService.futureWithDeadline(...)(Unknown Source)

---

maybe this topic is corrupted

for debugging purposes, can you try reverting

maxUnackedMessagesPerConsumer

to its original value and see if that fixes the issue?

yes if it reverted, it is back to normal.

after i reverted , the command worked

btw this is 3.0.11

conflict writing metadata to store

error is. gone as well . seems this may be the root cause

Enhancing Pulsar CI with Netty leak detection and reporting (dev mailing list thread: https://lists.apache.org/thread/fh63hg31womzr64bc7djv3sovgcx6z99) Hello all, Currently, Pulsar CI lacks the capability to systematically detect and report Netty buffer leaks. This creates a significant blind spot in our quality assurance process, as these leaks can slip through undetected until they manifest as performance degradation, resource exhaustion, or unpredictable failures in production environments. I've submitted a PR (#24272) that addresses this gap by implementing advanced Netty leak detection capabilities within our CI pipeline. The implementation follows a staged approach: 1. First, enable leak detection and reporting without failing CI builds 2. Fix identified leaks in both test and production code 3. Eventually, enable strict enforcement where CI builds would fail when leaks are detected The PR adds a custom ExtendedNettyLeakDetector implementation, configures it to output detailed reports to a designated directory, and adds reporting steps to all CI workflows to display leaks directly in the GitHub Actions UI. It also enhances the PulsarTestListener to trigger leak detection at key test lifecycle events and provides capabilities to collect and report leaks from integration tests. Most of the detected leaks are in test code, but some seem to be in production code. I've used this solution for the last couple of months to detect leaks in Pulsar code by running tests locally, and it works well. By catching these issues early in the development cycle, we can create an automated safety net that prevents future Netty buffer management regressions and significantly improves system stability and resource efficiency in production environments. Please review the PR at https://github.com/apache/pulsar/pull/24272. -Lari