thetumbled commented on PR #24339: URL: https://github.com/apache/pulsar/pull/24339#issuecomment-2911345261
> @thetumbled Do you have ordering requirements in your use case? If not, one possible solution could be to add a org.apache.pulsar.client.impl.MessageRouterBase implementation similar to org.apache.pulsar.client.impl.RoundRobinPartitionMessageRouterImpl which stops routing messages to a partition when the number of pending messages go over a "high water mark" threshold. It could resume routing to a partition after the pending messages go under a "low water mark" threshold. We don't have ordering requirements. Implementing a new route implementation could be a good choice. -- 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: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
