A little bit more info: The topic is partitioned, 3 partitions. The backlog quota is set to 50h The TTL is set to 48h.
This is the second time that we observe this error. The application reads from 5 different topics, but only one topic has been affected twice. This is the topic with the highest traffic processed by the same application. (Yet, our app is not really data intensive when compared to other use cases, it process less than 1 million events per hour) On Mon, Mar 21, 2022 at 8:13 AM Tecno Brain <cerebrotecnolog...@gmail.com> wrote: > > Hello > I am using Pulsar 2.8.0 > My application suddenly stopped processing messages, tries to reconnect > but keeps getting errors about BadVersion. > > We unloaded the topic and the application restarted processing messages. > (The application did not need to be restarted). > > Any idea what causes this? How to prevent it? > > Thank you. > > -Jorge > > [persistent://tenant/namespace/mytopic-partition-2] > [platform_persistent://tenant/namespace/mytopic] Could not get connection > to broker: java.util.concurrent.CompletionException: > org.apache.pulsar.broker.service.BrokerServiceException$PersistenceException: > org.apache.bookkeeper.mledger.ManagedLedgerException$BadVersionException: > org.apache.pulsar.metadata.api.MetadataStoreException$BadVersionException: > org.apache.zookeeper.KeeperException$BadVersionException: KeeperErrorCode = > BadVersion for > /managed-ledgers/tenant/namespace/persistent/my-topic-partition-2/platform_persistent%3A%2F%2Ftenant%2Fnamespace%2Fmytopic > -- Will try again in 0.1 s >
