suiyuzeng edited a comment on pull request #2891: URL: https://github.com/apache/bookkeeper/pull/2891#issuecomment-972791041
> Regarding garbage collection, retention is not determined by BookKeeper but whoever controls the ledger metadata (Pulsar for example). I don't think using a configured time period is the way to address this. The issue is that we try to store all metadata in memory, but given that each entry log has a ledger map, we can perform a scan process where we incrementally perform GC without all metadata in memory. Thanks for your suggestion. I meet the issue in puslar for iot. There are millions topics which has the retention time. It works well in this scene. But it may be not common way to the problem like this. A scan process is better for this. I will fix the issue in this way. -- 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]
