[Bug] When batching is enabled even when no data is being streamed CPU usage remains high post streaming to 1.5k topics

[salianvineet]

Search before asking

• I searched in the issues and found nothing similar.

Read release policy

• I understand that unsupported versions don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker.

Version

2.10.6

Minimal reproduce step

With batching enabled stream data to 1500 topics, then stop streaming and monitor the CPU usage
When batching is enabled

When batching is disabled

What did you expect to see?

CPU utilization should come down to 2-3% when data is not being streamed

What did you see instead?

CPU utilization is high even when data is not being streamed

Anything else?

This is seen only when batching is enabled. When batching is disabled it works as expected.

Are you willing to submit a PR?

• I'm willing to submit a PR!

[lhotari]

2.10.6

Pulsar 2.10.x is a very old and outdated version of Pulsar. Currently supported versions are 4.0.x, 3.3.x and 3.0.x.
Does this problem reproduce with a supported Pulsar broker version and supported Pulsar client version?