Describe the bug
We have 3 bookie and 2 zookeeper and 2 broker.
we were a 2.4.x but due to error readTimeException we upgraded to 2.9.1. Recently after restarting a consumer, consumer was connected to the pulsar but no messages were pulled. (Consumer was creating a websocket connection in pull mode)
We observed that the broker process cpu was beyond 600- 700 without any load and hence no messages are consumed even with consumer connected.
Ever post restart the broker issue is still the same . We downgraded to 2.8.2 but still have the same issue.
To Reproduce
Steps to reproduce the behavior:
1: install 2.8.2
2: create 200-300 consumer
Expected behavior
Consumer should be able to consume messages post connection.
Original Issue: apache/pulsar#14660
Describe the bug We have 3 bookie and 2 zookeeper and 2 broker. we were a 2.4.x but due to error readTimeException we upgraded to 2.9.1. Recently after restarting a consumer, consumer was connected to the pulsar but no messages were pulled. (Consumer was creating a websocket connection in pull mode) We observed that the broker process cpu was beyond 600- 700 without any load and hence no messages are consumed even with consumer connected. Ever post restart the broker issue is still the same . We downgraded to 2.8.2 but still have the same issue.
To Reproduce Steps to reproduce the behavior: 1: install 2.8.2 2: create 200-300 consumer
Expected behavior Consumer should be able to consume messages post connection.
Screenshots
Desktop (please complete the following information): Ubuntu
Additional context Add any other context about the problem here.