michalcukierman opened a new issue, #23299: URL: https://github.com/apache/pulsar/issues/23299
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [X] 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 3.3.1 ### Minimal reproduce step I was not able to create a reproducible example yet. The situation happened on one of our test environments, on: - partitioned topic (each of 6 partition is affected) - two producers writing to a topic - first producer uses: LZ4, Batching, eventTime, message properties, and both: nullable and non-nullable payload - second producer uses: Batching, eventTime, message properties, and both: nullable and non-nullable payload The error Message: <img width="1457" alt="Screenshot 2024-09-12 at 17 46 32" src="https://github.com/user-attachments/assets/c77fc108-0321-42f7-a477-e3ba445074e4";> Queries showing activity of __subscription consumers and failed compaction <img width="1725" alt="Screenshot 2024-09-12 at 17 47 20" src="https://github.com/user-attachments/assets/08beee7c-7f01-4b00-af83-59cbd3184bec";> Constant backlog of the messages: <img width="1722" alt="Screenshot 2024-09-12 at 17 48 36" src="https://github.com/user-attachments/assets/e71840eb-fd24-44b6-a183-ee87931e025a";> Stacktrace comes from the recent update of `[RawBatchConverter.java](https://github.com/apache/pulsar/pull/21917/files#diff-91cd32cbdf605810629e9890fb5dd1ee8d7bbee85038aaeb7919ce52a3649f58)` ### What did you expect to see? The topics are compacted ### What did you see instead? Compaction on every topic fails, what causes the server to try to compact again. ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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]
