szkoludasebastian commented on issue #23908: URL: https://github.com/apache/pulsar/issues/23908#issuecomment-2647586739
I did some more tests and it turned out that it is most likely the version of pulsar client that is causing the problem. Previously when I was testing pulsar server all the time the client was version 4.0.1 and I managed to reproduce the issue. After all these tests of pulsar server I decided to check if it wasn't the client that was causing it so I reverted to client 3.3.2 and this time I wasn't able to reproduce the issue when restarting bookies, only restarting brokers caused stuck partitions (but it was really random). I have posted all the results of my tests below. | Server | Client | Result | Notes | | -------- | ------- | ------ | ------- | | 3.3.2 | 3.3.2 | no issue on bookies restart. When I restart brokers then I see stuck partitions | partitions backlog is not growing fast, it's rather really low | 3.3.2 | 3.2.4 | no issue on bookies restart. When I restart brokers then I see stuck partitions <img width="400" alt="Image" src="https://github.com/user-attachments/assets/8b40b975-6adc-4c0e-b3eb-8c1228df248b"; /> | partitions backlog is not growing fast, it's rather really low | 3.3.2 | 4.0.1 | issue reproduced with bookies restart <img width="352" alt="Image" src="https://github.com/user-attachments/assets/2021db4d-db13-4bf5-a170-5d3d057705a3"; /> | Immediately noticeable increase in partitions backlog | 4.0.1 | 4.0.1 | issue reproduced with bookies restart <img width="358" alt="Image" src="https://github.com/user-attachments/assets/66e9d817-0ff8-4721-88c0-f91532f00f38"; /> | Immediately noticeable increase in partitions backlog -- 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]
