Product Quota
Last updated: 2025-12-24 15:07:56
Why Does the Error Topic reached max producers limit Occur When I Initialize the Producer Client?
This error occurs because the number of producers created for the current topic has reached the upper limit. To ensure cluster stability, the number of producers per topic cannot be increased indefinitely. For the producer upper limit per partition of a topic, see Quotas and Limits. If you need to increase the number of producers, you can submit a ticket for evaluation and adjustment.
Why Does the Error Subscription reached max consumers limit Occur When I Initialize the Subscription/Consumer Client?
This error occurs because the number of consumers created for the current topic has reached the upper limit. To ensure cluster stability, the number of consumers per topic and per subscription cannot be increased indefinitely. For the consumer upper limits of topics and subscriptions, refer to Quotas and Limits. If you need to increase the number of consumers, you can submit a ticket for evaluation and adjustment.
Why Does the Error The backlog quota of the topic xxx is exceeded Occur When the Current Virtual Cluster Producer Produces to a Topic?
The complete error log states:
server error: ProducerBlockedQuotaExceededException: Cannot create producer ontopic with backlog quota exceeded. Virtual clusters have a configured message backlog upper limit of 10 GB per topic partition (see Quotas and Limits). If a topic partition exceeds this message backlog upper limit, a production error occurs, preventing further message production. Common solutions include:1. Check the console for message gaps across all subscriptions of the topic. If message gaps are found, investigate the reasons why clients are not sending acknowledgments and restart the corresponding clients to trigger message redelivery.
2. Increase the number of consumers to boost the consumption speed for each subscription under the topic.
3. Shorten the time-to-live (TTL) of the namespace where the topic resides, or modify the current consumption offset. This allows unconsumed messages to be automatically acknowledged by the server. Note that both methods result in the server automatically acknowledging messages, meaning these messages will not be pushed to the client.
4. Upgrade to a pro cluster, which does not have the 10 GB message backlog limit.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback