道君

@lhotari how about add a new method `seek(long timestamp, boolean speedUp)` to `Consumer` api? If `speedUp=true`, enable speed up seeking by using `LedgerInfo`, else, disable. It should be more flexible

> > @lhotari how about add a new method `seek(long timestamp, boolean speedUp)` to `Consumer` api? If `speedUp=true`, enable speed up seeking by using `LedgerInfo`, else, disable. It should be...

> I disagree that "pass it to ML doesn't make sense". it's already passed in and used to evaluate seek. There would need to to have the min, max, first...

@lhotari I've updated the implementation, PTAL

Moved to https://github.com/apache/pulsar/pull/21771, close this as inactive

@BalajiLaks It seems that this PIP has been blocked for a long time, please send a VOTE mail to the mail list

it looks like ML read entries from an already closed ledger, read entries from a closed ledger will lead to exception, and then, ML will try to close the ledger...

@graysonzeng could please provide the steps that I can reproduce the issue？

@graysonzeng what's your pulsar version? could you please provide more log?

Closing `Handle` multiple times does indeed occur frequently, because `ledger#closeAsync` is called by async thread when read entries failed, if there are some ongoing read operations, they will also try...