TakaHiR07 opened a new pull request, #4529: URL: https://github.com/apache/bookkeeper/pull/4529
### Motivation One of our cluster occur a case that read ledger LAC timeout and ledger can not recover, which make topic unavailable. After adding extra log in bookie-server, we finally found the bottleneck is in EntryLocationIndex#getLastEntryInLedgerInternal, it spend 2.5 minute to scan the rocksdb.  Currently it may be hard to find out the bottleneck is in getLastEntryInLedgerInternal. Because if getLastEntryInLedgerInternal throw noEntry exception, the read-locations-index-time is not able to record the long latency. There is no way to know the bottleneck is in getLastEntryInLedgerInternal.   Because once the bottleneck in getLastEntry occur, the worst it would cause ledger unavailable and pulsar topic unavailable, I think is important to add this metric ### Changes add metric. -- 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]
