lhotari opened a new issue, #25212: URL: https://github.com/apache/pulsar/issues/25212
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation [PIP-234](https://github.com/apache/pulsar/issues/19074) enables sharing of Pulsar client resources across multiple isolated Pulsar client instances. This was implemented in #24784 and #24790. The solution lacks limiting the total amount of memory across all of the Pulsar client instances. That would be useful when memory limiting relies on the memory limit controller. ### Solution Modify `org.apache.pulsar.client.api.PulsarClientSharedResources` interface and implementation to support sharing memory limit controller in the same way as other shared resources are configured without directly referencing implementation instances. Modify the current `MemoryLimitController` to support sharing. It would require support for registering multiple `trigger` callbacks and deregistering the callback when the client instance gets closed. ### Alternatives _No response_ ### 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]
