On Thu, 7 Mar 2024 at 08:14, Girish Sharma <scrapmachi...@gmail.com> wrote: > There is for 310 - > https://lists.apache.org/thread/13ncst2nc311vxok1s75thl2gtnk7w1t
Girish, thank you for sharing the link to the PIP-310 thread. We also met in community meetings to discuss PIP-310 (https://lists.apache.org/thread/y1sqpyv37fo0k4bm1ox28wggvkb7pbtw). I believe PIP-310 is a successful example of excellent community collaboration. With PIP-310, Girish provided insightful feedback and also presented a thorough analysis of the Pulsar Rate Limiters. As a first step, this led to PIP-322, Pulsar Rate Limiting Refactoring (https://github.com/apache/pulsar/blob/master/pip/pip-322.md). PIP-322 has been implemented and delivered in Pulsar 3.2.0. There are also plans to continue the improvements with the next set of enhancements following PIP-322 (refer to: https://lists.apache.org/thread/rj14rmzd5z5sy7kfg22kt4l5dzjwk9vn) and to cover the original requirements behind PIP-310. I'm looking forward to continuing this collaboration to deliver further improvements to the existing multi-tenancy features. The areas of improvement are service level management and capacity management of a large Pulsar system. This is also a key concern of messaging-as-a-service / streaming-as-a-service platform teams that build upon Apache Pulsar. -Lari
