istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Change rate limit to 1qps

This commit is contained in:
mandarjog 2017-05-11 13:32:23 -07:00 committed by GitHub
parent e53255aa15
commit a5af2ecc47
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
_docs/tasks/rate-limiting.md
View File

@ -48,8 +48,8 @@ Using Istio we can ensure that `1qps` is not breached.
params:
quotas:
- descriptorName: RequestCount
maxAmount: 5
expiration: 5s
maxAmount: 1
expiration: 1s
```
`istioctl` sets configuration for `subject=ratings.default.svc.cluster.local`
@ -70,7 +70,7 @@ In the previous example we applied a rate limit to the `ratings` service without
to any other attributes. It is possible to conditionally apply rate limits based on
attributes like the source of the traffic.
The following configuration applies a `5qps` rate limit only to version `v3` of `reviews`.
The following configuration applies a `1qps` rate limit only to version `v3` of `reviews`.
1. Configure mixer with the conditional rate limit:
@ -86,8 +86,8 @@ The following configuration applies a `5qps` rate limit only to version `v3` of
params:
quotas:
- descriptorName: RequestCount
maxAmount: 5
expiration: 5s
maxAmount: 1
expiration: 1s
```
2. Generate load on the `productpage` with the following command:
@ -99,7 +99,7 @@ The following configuration applies a `5qps` rate limit only to version `v3` of
generator is running (i.e., generating more than 1 req/s), the traffic generated by
your browser will be rate limited.
Since the `reviews-v3` service is unable to access the `ratings` service freely, we stop seeing `red` stars on the UI.
Since the `reviews-v3` service is unable to access the `ratings` service freely, we should see `red` stars very infrequently.
## Understanding rate limits