You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we set clientRebalance as false, we can noly control consumption rate by following configurations:
consumeThreadMin
consumeThreadMax
In some scenarios, even a single thread may exceed the consumption rate that the business can accept. And it is difficult to calculate how many threads should be set based on the consumption rate
Generally, developers use RateLimiter to control the rate in the consumer listener, but this can easily lead to consume-timeouts. It is best to provide this function within the SDK.
Describe the Solution You'd Like
Developers can set following configurations to control consumption rate:
enableConsumeRateLimit=true
// 10 qps/s for single consumer
consumptionRate=10
Describe Alternatives You've Considered
Use RateLimiter to control rate in the messageListener
Is Your Feature Request Related to a Problem?
If we set clientRebalance as false, we can noly control consumption rate by following configurations:
In some scenarios, even a single thread may exceed the consumption rate that the business can accept. And it is difficult to calculate how many threads should be set based on the consumption rate
Generally, developers use
RateLimiter
to control the rate in the consumer listener, but this can easily lead to consume-timeouts. It is best to provide this function within the SDK.Describe the Solution You'd Like
Developers can set following configurations to control consumption rate:
Describe Alternatives You've Considered
Use
RateLimiter
to control rate in the messageListenerAdditional Context
The text was updated successfully, but these errors were encountered: