The QuotaSchedulingPolicy CustomResourceDefinition (CRD) provided by the Service Mesh (ASM) traffic scheduling suite defines a policy that implements priority-based request scheduling after the specified request quota is reached. This topic describes the fields of QuotaSchedulingPolicy.
Overview
QuotaSchedulingPolicy specifies the configuration of the rate limiter used for scheduling and the scheduler that schedules requests based on their priorities after throttling is triggered.
QuotaSchedulingPolicySpec
QuotaSchedulingPolicySpec is the core configuration of QuotaSchedulingPolicy and corresponds to the spec field.
Field | Type | Required | Description |
quota_scheduler | Yes | Specifies the configuration of the rate limiter and the priority-based scheduler used by the request quota-based scheduling policy. |
QuotaScheduler
Field | Type | Required | Description |
fill_amount | double | Yes | The number of tokens filled into the token bucket each time. You can implement throttling by specifying this field together with the |
bucket_capacity | double | Yes | The maximum capacity of the token bucket used by the rate limiter. When the request rate is lower than the token bucket filling rate, the number of tokens in the token bucket will continue to increase until the maximum capacity specified by the |
rate_limiter | Yes | The configuration of the rate limiter that is used by the request quota-based scheduling. | |
scheduler | Yes | The configuration of the priority-based scheduler that is used to queue requests when the request rate exceeds the upper limit. | |
selectors | []Selector | Yes | The selector used to select specific requests for which throttling takes effect. |