The default workload group has the following policy defined by default. The following policies will block all requests classified to the workload group: [
500 concurrent requests for the workload group. 
The exception type will be QuotaExceededException. Resource: 'TotalCpuSeconds', Quota: '2000', TimeWindow: '01:00:00', Origin: 'RequestRateLimitPolicy/WorkloadGroup/Automated Requests'. The request was denied due to exceeding quota limitations. Resource: 'RequestCount', Quota: '1000', TimeWindow: '01:00:00', Origin: 'RequestRateLimitPolicy/WorkloadGroup/Automated Requests/Principal/aadapp=9e04c4f5-1abd-48d4-a3d2-9f58615b4724 6ccf3fe8-6343-4be5-96c3-29a128dd9570'.Ī throttled request, that was classified to a workload group named Automated Requests, which has a limit of 2000 total CPU seconds per hour at the scope of the workload group. The following table shows a few examples of requests that exceed the resource utilization rate limit and the error message that these requests return: ScenarioĪ throttled request that was classified to a workload group named Automated Requests, which has a limit of 1000 requests per hour at the scope of a principal. The error message will include the origin of the throttling and the quota that's been exceeded. When a request exceeds the limit on resources utilization: The sliding time window during which the limit is applied. The maximum of the resource that can be utilized. Requests that report utilization of 0.005 seconds of CPU or lower are not counted. Note: when ResourceKind is TotalCpuSeconds, the limit is enforced based on post-execution reports of CPU utilization of completed requests: Requests whose execution will begin after MaxUtilization has been reached within the defined TimeWindow (based on reporting of completed requests) will fail. Resource utilization rate limitĪ request rate limit of kind ResourceUtilization includes the following properties: Name The exception type will be QueryThrottledException for queries, and ControlCommandThrottledException for control commands.Ĭontrol commands may also be throttled as a result of exceeding the limit defined by the cluster's capacity policy. 
Retrying after some backoff might succeed. Capacity: 50, Origin: 'RequestRateLimitPolicy/WorkloadGroup/MyWorkloadGroup'.Ī throttled query that was classified to a workload group named MyWorkloadGroup, which has a limit of 10 concurrent requests at the scope of a principal. CommandType: 'TableCreate', Capacity: 80, Origin: 'RequestRateLimitPolicy/WorkloadGroup/default'.Ī throttled query that was classified to a workload group named MyWorkloadGroup, which has a limit of 50 concurrent requests at the scope of the workload group.
The control command was aborted due to throttling. create table command that was classified to the default workload group, which has a limit of 80 concurrent requests at the scope of the workload group. The following table shows a few examples of concurrent requests that exceed the maximum limit and the error message that these requests return: ScenarioĪ throttled. The error message will include the origin of the throttling and the capacity that's been exceeded.The request's state, as presented by System information commands, will be Throttled.When a request exceeds the limit on maximum number of concurrent requests: The maximum number of concurrent requests. Indicates if the policy is enabled or not.Ī request rate limit of kind ConcurrentRequests includes the following property: Name The policy objectĪ request rate limit policy has the following properties: Name The workload group's request rate limit policy lets you limit the number of concurrent requests classified into the workload group, per workload group or per principal.
0 kommentar(er)
