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

Fix circuit-breaker snips (#7475)

This commit is contained in:
Frank Budinsky 2020-06-04 22:23:44 -04:00 committed by GitHub
parent 4fd4e02bd6
commit 1d5fa543ef
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/tasks/traffic-management/circuit-breaking/index.md
View File

@ -193,7 +193,7 @@ one connection and request concurrently, you should see some failures when the
1. Bring the number of concurrent connections up to 3:
{{< text bash >}}
$ kubectl exec -it "$FORTIO_POD" -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 30 -loglevel Warning http://httpbin:8000/get
$ kubectl exec -it "$FORTIO_POD" -c fortio -- /usr/bin/fortio load -c 3 -qps 0 -n 30 -loglevel Warning http://httpbin:8000/get
20:32:30 I logger.go:97> Log level is now 3 Warning (was 2 Info)
Fortio 1.3.1 running at 0 queries per second, 6->6 procs, for 30 calls: http://httpbin:8000/get
Starting at max qps with 3 thread(s) [gomax 6] for exactly 30 calls (10 per thread + 0)

2
content/en/docs/tasks/traffic-management/circuit-breaking/snips.sh
View File

@ -151,7 +151,7 @@ Code 503 : 3 (15.0 %)
ENDSNIP
snip_tripping_the_circuit_breaker_3() {
kubectl exec -it "$FORTIO_POD" -c fortio /usr/bin/fortio -- load -c 3 -qps 0 -n 30 -loglevel Warning http://httpbin:8000/get
kubectl exec -it "$FORTIO_POD" -c fortio -- /usr/bin/fortio load -c 3 -qps 0 -n 30 -loglevel Warning http://httpbin:8000/get
}
! read -r -d '' snip_tripping_the_circuit_breaker_3_out <<\ENDSNIP