Mateusz Tworek
Mateusz Tworek
@StevenLuMT Thank you for responding. I understand why you might think that way; however, please refer to the sample logs provided below and at the bottom. We have experienced multiple...
@StevenLuMT Yeah, that's how it looks to me. Obviously I can't share the whole file, but are there any commands to verify its consistency?
@StevenLuMT I've tried, but seems like the ledger is long gone.: ```shell kubectl exec -n pulsar pod/pulsar-bookie-4 -- /pulsar/bin/bookkeeper shell readlog 1884 > ./1884_meta.log # there are 7005 entries ❯...
@StevenLuMT I assume you meant (flags with double dash, readledger command): ```shell bookieId=pulsar-bookie-4.pulsar-bookie.pulsar.svc.cluster.local:3181 lid=17772 eidStart=0 eidEnd=7005 /pulsar/bin/bookkeeper shell readledger --bookie $bookieId --msg --ledgerid $lid --firstentryid $eidStart --lastentryid $eidEnd ``` Same...
@StevenLuMT ```shell pulsar-bookie-4:~/bookkeeper/ledgers/current$ lid=17772 pulsar-bookie-4:~/bookkeeper/ledgers/current$ /pulsar/bin/bookkeeper shell ledgermetadata -ledgerid $lid ... 2025-04-25T07:11:22,398+0000 [main] ERROR org.apache.bookkeeper.bookie.BookieShell - Got an exception com.google.common.util.concurrent.UncheckedExecutionException: java.util.concurrent.ExecutionException: org.apache.bookkeeper.client.BKException$BKNoSuchLedgerExistsOnMetadataServerException: No such ledger exists on Metadata Server ```...
@StevenLuMT Current entryLog has multiple different ledgerIds mentioned in the metadata. Our cluster is not massive, but we have multiple topics that should be constantly active. It feels strange that...
Hey @eolivelli @hangc0276 @zymap, Just wanted to let you know that is still seems to be a thing. We are using: `Pulsar 4.0.0` With `Apache Bookie 4.17.1` Deployed via `https://pulsar.apache.org/charts`...
@olix0r sure, are you looking for `version`? It was `2.280.0` for affected pods. Additionally I wanted to underline that it seems to be just a side effect of the upgrade...
@cratelyn happy to help, errors in prometheus logs started right after resources generated via new chart were applied in our cluster: - pods present during chart upgrade, injected with `2025.2.1`...