mrtworo commented on issue #4596:
URL: https://github.com/apache/bookkeeper/issues/4596#issuecomment-2829594114
@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
```
Some random fresh ledger just to confirm the command works:
```shell
pulsar-bookie-4:~/bookkeeper/ledgers/current$ /pulsar/bin/bookkeeper shell
ledgermetadata -ledgerid 18374 | grep LedgerMetadata
2025-04-25T07:08:11,871+0000 [main] INFO
org.apache.bookkeeper.tools.cli.commands.client.LedgerMetaDataCommand -
LedgerMetadata{formatVersion=3, ensembleSize=3, writeQuorumSize=3,
ackQuorumSize=2, state=OPEN, digestType=CRC32C, REDACTED
```
So still the same, we had some experience with these components already, so
I'm pretty sure it's just not there, checking from metadata side as well:
>[zk: pulsar-zookeeper:2181(CONNECTED) 11] ls /ledgers/00/0001/L7772
Node does not exist: /ledgers/00/0001/L7772
It shouldn't be a problem during compaction right? If bookie discovers that
entries are not a part of active ledger they should be considered for removal
during compaction if threshold is met.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
