Please note that 40501 errors seen due to hard throttling on worker threads and due to throttling on other resources will continue to be seen as before. Please ensure your error catching logic continues to handle these 40501s as before.
|Current mechanism : Worker thread throttling||New mechanism : Worker thread governance (coming soon)|
When soft throttling limit for worker threads on a machine is exceeded, the database with the highest requests per second is throttled. Existing connections to that database are terminated if new requests are made on those connections, and new connections to the database are denied, until number of workers drops below soft throttling limit.
Every database will have a maximum worker thread concurrency limit. *
Please note this limit is only a maximum cap and there is no guarantee that a database will get threads up to this limit, if the system is too busy.
|Error returned||40501 :The service is currently busy. Retry the request after 10 seconds.Incident ID: <ID>. Code: <code>.||
: Resource ID: %d. The %s limit for the database is %d and has been reached. See
Back-off and retry request after 10 seconds;
to view which user requests are currently executing
Note : The hard throttling on worker thread mechanism is not being changed and will continue to return a 40501 error to user applications.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.