Forum Discussion
Controlling an Application’s Throughput Consumption in Cosmos DB with ThroughputControlGroup
Hi Azure Cosmos Db Team, Was referring to the below document link to limit the throughput consumption per requests. https://the9090rule.medium.com/controlling-an-applications-throughput-consu...
HI Team,
Just following up on the same regarding throughputcontrolgroup behavior?
With Regards,
Nitin Rahim
Just following up on the same regarding throughputcontrolgroup behavior?
With Regards,
Nitin Rahim
mannu2050
Microsoft
Microsoftnitinrahim Yes, the throughput control group feature does the throttling on the client side when the target throughput or target throughput threshold is exceeded.
Hope this helps!
- Hi Manish,
Thanks for your response.
What would be default client side throttling behavior if we are using JAVA SDK? What will be the error returned before hitting the cosmos db in case of client side throttling ? Will it return a status code 429 after a cumulative wait time of 30 seconds? Will it retry 9 times(default sdk times)? And other transactions which are not in the througputcontrolgroup will be unaffected during this client side throttling right if that not exceeds the RU's allocated?
Thanks in advance.
With Regards,
Nitin Rahim- Hi Team,
Good morning. Just following up on the above question?
With Regards,
Nitin Rahim- mannu2050
nitinrahim throughput control will only try to restrict the throughput of the operation you define under it and will not impact other operations. It will generate the throttling error which will be handled by SDK as a regular throttling by means of retries / exception after retry. Please note this config does not calculate the RUs before executing the operation instead it checks the usage after the operation gets executed so a single operation may breach the RUs constraint.
Hope this helps!