berg223 commented on code in PR #24400:
URL: https://github.com/apache/pulsar/pull/24400#discussion_r2135784096


##########
pip/pip-426.md:
##########
@@ -0,0 +1,163 @@
+
+# PIP-426: Enhanced Consumer Throttling and Unacknowledged Message Tracking 
for Exclusive and Failover Subscriptions
+
+# Background knowledge
+
+<!--
+Describes all the knowledge you need to know in order to understand all the 
other sections in this PIP
+
+* Give a high level explanation on all concepts you will be using throughout 
this document. For example, if you want to talk about Persistent Subscriptions, 
explain briefly (1 paragraph) what this is. If you're going to talk about 
Transaction Buffer, explain briefly what this is. 
+  If you're going to change something specific, then go into more detail about 
it and how it works. 
+* Provide links where possible if a person wants to dig deeper into the 
background information. 
+
+DON'T
+* Do not include links *instead* explanation. Do provide links for further 
explanation.
+
+EXAMPLES
+* See [PIP-248](https://github.com/apache/pulsar/issues/19601), Background 
section to get an understanding on how you add the background knowledge needed.
+  (They also included the motivation there, but ignore it as we place that in 
Motivation section explicitly).
+-->
+
+Apache Pulsar currently lacks full support for enforcing unacknowledged 
message limits and consumer-side flow control in exclusive and failover 
subscriptions. While these mechanisms function correctly for shared 
subscriptions, their absence in exclusive/failover modes causes critical 
limitations:
+

Review Comment:
   Yes. It's also benefit to solve similiar issues to #15189.  The draining 
approach could also be implemented .  Your comments always open my mind and 
point me in the right direction !



-- 
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]

Reply via email to