[ https://issues.apache.org/jira/browse/ROCKETMQ-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943346#comment-15943346 ]
ASF GitHub Bot commented on ROCKETMQ-106: ----------------------------------------- Github user lizhanhui commented on the issue: https://github.com/apache/incubator-rocketmq/pull/66 What I intend to deliver is that it's always good to have simple API, but it would be miserably unexpected to change semantics of a configuration quietly. Further, it's best not to introduce overhead for the features application developers may not need. This is why I suggest to introduce a boolean switch to short circuit it on default at the very beginning. > Add flow control on topic level > ------------------------------- > > Key: ROCKETMQ-106 > URL: https://issues.apache.org/jira/browse/ROCKETMQ-106 > Project: Apache RocketMQ > Issue Type: Wish > Components: rocketmq-client > Reporter: Jaskey Lam > Assignee: Jaskey Lam > > *Motivations* > For current flow control, we can only control on queue level. > Howerver, the numbers of queue allocated may be dynamic changed. For example, > I might hope to control that at most 1000 messages can be pulled from broker > to protect my client. And I have no idea how many queue I am allocated. Maybe > I will have 5 queue and 5 instances so I set `pullThresholdForQueue`=1000, > which works as expected when one is fine. But as long as any instances > crashes, some instances may be allocated more than one queue, which will > make messages pulled from broker exceed my expectations. > A configuration of `pullThresholdForTopic` is propably most user hopes. -- This message was sent by Atlassian JIRA (v6.3.15#6346)