mrtworo commented on PR #4021: URL: https://github.com/apache/bookkeeper/pull/4021#issuecomment-2809794040
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` Storage was constantly growing on the affected bookie, when triggering compaction manually via: `curl -X PUT http://localhost:8000/api/v1/bookie/gc` I've seen same pattern in the logs: ``` 2025-04-16T14:28:10,211+0000 [GarbageCollectorThread-6-1] INFO org.apache.bookkeeper.bookie.GarbageCollectorThread - GarbageCollectorThread-6-1 Set forceGarbageCollection to false after force GC to make it forceGC-able again. 2025-04-16T14:28:10,152+0000 [GarbageCollectorThread-6-1] INFO org.apache.bookkeeper.bookie.DefaultEntryLogger - Failed to get ledgers map index from: 4503.log : Negative position 2025-04-16T14:28:10,152+0000 [GarbageCollectorThread-6-1] DEBUG org.apache.bookkeeper.bookie.DefaultEntryLogger - Recovering ledgers maps for log 4503 at offset: -1 2025-04-16T14:28:10,151+0000 [GarbageCollectorThread-6-1] INFO org.apache.bookkeeper.bookie.GarbageCollectorThread - Extracting entry log meta from entryLogId: 4503 ``` when entry log was moved to backup location: ``` #dec 4503 -> hex 1197 pulsar-bookie-2:~/bookkeeper/ledgers/current$ ls bkp/ 1197.log ``` compaction went fine and reclaimed expected storage. -- 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]
