Hi, Pulsar broker can face high CPU and GC Impact due to change made in PIP-91 to log huge exception stacktrace for PulsarClientException. Detailed issue is described at : https://github.com/apache/pulsar/issues/23250. PulsarClientException tries to create and keep list of past Exception objects into memory and then tries to generate large stacktrace by iterating over each exception which consumes lot of system CPU and also generates lot of garbage that significantly increases GC pauses on broker. Therefore, we will need PR: https://github.com/apache/pulsar/pull/23251 which will reduce the Exception stacktrace by not including past-exception message which can be anyway found in logs and that will help to avoid storing and generating such past exception objects, and reducing CPU and GC impact on brokers.
Thanks, Rajan
