smbecker opened a new issue, #217: URL: https://github.com/apache/pulsar-dotpulsar/issues/217
### Is your feature request related to a problem? Please describe I am looking to leverage [KEDA](https://keda.sh/) to support auto-scaling my Pulsar consumers based on topic volumes. One of the [best practices](https://keda.sh/docs/2.14/concepts/scaling-deployments/#leverage-the-container-lifecycle) with regards to properly handling requests to scale down would involve preventing the `MessageProcessor` from receiving new messages while allowing any messages that are currently in-flight (or have already been processed but not yet acknowledged) from continuing and sending the acknowledgement back to the broker. After reviewing the code, I can't seem to find a way to handle that. ### Describe the solution you'd like and alternatives you've considered Add support for a mechanism to prevent the `MessageProcessor` from picking up new messages while allowing already pulled messages to continue. In the meantime, I can leverage [scale as job](https://keda.sh/docs/2.14/concepts/scaling-jobs/) to work-around this issue. -- 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.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
