in the same time I also saw errors from zookeeper: 2023-07-16T103713,982+0000 [NIOWorkerThread-4] WARN org.apache.zookeeper.server.NIOServerCnxn - Unexpected exception pulsar-zookeeper-2 pulsar-zookeeper org.apache.zookeeper.server.ServerCnxn$EndOfStreamException: Unable to read additional data from client

BTW: I saw I can increase

maxMessageSize

by adding that variable to broker configMap you think that would help in my case? Also I saw these errors in services which use the pulsar: logtime=“2023 07 16T1029:14Z” level=error msg=“Failed to create producer at send PRODUCER request” error=“server error: ServiceNotReady: Namespace bundle for topic (persistent://ourTenant/namespace/some-topic) not served by this instance. Please redo the lookup. Request is denied: namespace=ourTenant/namespace” producerID=1 producer_name=pulsar-1784-97 topic=“persistent://ourTenant/namespace/some-topic”

Hi! Only a few days left to submit your talk proposals to the Pulsar Summit North America. Don't miss your opportunity to share your Pulsar adventures in person in San Francisco! https://sessionize.com/pulsar-summit-north-america-2023

This message was deleted.

This message was deleted.

(its not clear from the bookkeeper configuration doc)

This message was deleted.

This message was deleted.

Hi, Any idea what are these errors:

pulsar-clusters-bookie-1 pulsar-clusters-bookie 2023-07-20T15:17:28,435+0000 [BookKeeperClientWorker-OrderedExecutor-5-0] ERROR org.apache.bookkeeper.proto.PerChannelBookieClient - Read for failed on bookie pulsar-clusters-bookie-2.pulsar-clusters-bookie.pulsar-pcq-default.svc.cluster.local:3181 code EIO

pulsar-clusters-bookie-2 pulsar-clusters-bookie 2023-07-20T15:23:05,230+0000 [BookKeeperClientWorker-OrderedExecutor-7-0] ERROR org.apache.bookkeeper.client.ReadLastConfirmedOp - While readLastConfirmed ledger: 255 did not hear success responses from all quorums, QuorumCoverage(e:2,w:2,a:1) = [0, -1]

We are getting these constantly from our bookies More important is, how should I act when I encounter this error I already tried restarting the bookie statefulSet which didn’t change anything

@Moty which log are these errors in? Broker or bookie?

Bookie

Which bookie, 0, 1, 2? This looks like bookie2 is unreachable from the other bookies. So I would a) confirm that is the case in the other bookie logs, b) Confirm that bookie2 process is healthy and listening on port 3181 using

kubectl log

etc, and c) check networking, i.e. does the

clusters-bookie-2.pulsar-clusters-bookie.pulsar-pcq-default.svc.cluster.local

name resolve to the correct IP in DNS lookup etc.

Hi, I was wondering if there's any recommendations on how to handle adding new input topics to an existing function? When I attempt to do this I get the following error:

HTTP 400 {"reason":"Input Topics cannot be altered"}

... is there any configuration option somewhere to enable this? Or is the intent for us to delete and recreate the function when we need to add input topics? Or maybe define a new function using the same archive but with the new input topic(s)?

This message was deleted.

Reminder: today is the deadline!

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.