AnonHxy commented on PR #20001: URL: https://github.com/apache/pulsar/pull/20001#issuecomment-1507987446
> > When there are too many read request to bookie server, we need find out which ledger is reading without cache. > > @AnonHxy - was there not a bookie metric for this? Also, can you clarify why the existing cache metrics are insufficient? Sorry for the late reply @michaeljmarshall . It seems that we couldn't find out which topic or ledgerId is reading without cache from the bookie metric. Because there is no ledger tag in the booke metric. So This added metric will be useful to find out which topic is reading without cache. For example, a catch-up reading suddenly happens in our pulsar cluster. And too many reading requests will slow down the bookie cluster. From this added metric we could find out the topic and do something to deal with it -- 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]
