Re: [ANNOUNCE] Apache Pulsar 2.9.2 released

The release notes refers to 2.10.0 instead of 2.9.2 Thanks Tamer On Mon, 18 Apr 2022, 07:25 Ran Gao, wrote: > The Apache Pulsar team is proud to announce Apache Pulsar version 2.9.2. > > Pulsar is a highly scalable, low latency messaging platform running on > commodity hardware. It provides sim

All topic consumers are not receiving messages after upgrade to 2.8.3

Hi Team, After upgrading from 2.7.4 to 2.8.3 , we see all subscribers are no longer receiving messages , while producers can produce normally. No errors at consumers side , only log info that consumer has been successfully created for a topic , then wait forever at the receive() call , although

Re: broker v 2.8.3 failed to start with missing jar error

I found out the issue at my side , sorry about that. Thanks and Best Regards Tamer On Fri, Mar 25, 2022 at 3:58 PM tamer Abdlatif wrote: > Hi Team, > > I installed broker 2.8.3 and when try to start it fails with below error > > ls: cannot access > /opt/pulsar/apach

broker v 2.8.3 failed to start with missing jar error

Hi Team, I installed broker 2.8.3 and when try to start it fails with below error ls: cannot access /opt/pulsar/apache-pulsar-2.8.3/lib/org.aspectj-aspectjweaver-*.jar: No such file or directory Error opening zip file or JAR manifest missing : Error occurred during initialization of VM agent libr

Re: Broker freeze for communications in v 2.7.4

ithub.com/lhotari/28f71311f9dccc7dd2c0ef267b0242b1 > . > > Other questions: > What type of deployment do you have? Is it k8s? Is it deployed with Apache > Pulsar Helm chart? Do you access the Pulsar Broker via the Pulsar Proxy? > > -Lari > > On 2022/03/23 12:48:16 t

Broker freeze for communications in v 2.7.4

Hi everyone, We saw strange behaviour , as broker stopped accepting connections and client start receiving Connection Already Closed or Topic not available exceptions. The broker java process itself is up and running, but curl http ports such as curl broker metrics stop return anything. It is

Received error from server: Namespace bundle for topic xxx not served by this instance. Please redo the lookup. Request is denied

Hi Team, We are running our consumer application as pods in Kubernetes ..3/5 of our consumers are working fine , however ,2/5 are receiving the subject error . Any idea what could be the root cause for that error ? Your quick response is highly appreciated Thanks and best regards, Tamer

Re: [VOTE] PIP-135: Include MetadataStore backend for Etcd

Will that affect the existing ZK metadata in a pulsar instance , When we upgrade from a lower version to 2.10 ? In other words, Do we need a metadate migration to switch from ZK to Etcd ? Thanks Tamer On Fri, 14 Jan 2022, 22:52 Matteo Merli, wrote: > https://github.com/apache/pulsar/issues/