Alibaba Cloud Service Mesh:Configure circuit breaking for inter-service traffic with ASMCircuitBreaker

ASM console

1. On the Mesh Management page, click the name of the ASM instance. In the left-side navigation pane, choose Traffic Management Center > VirtualService. Click Create.

2. Select a namespace from the Namespace drop-down list and enter a name in the Name field. In the Gateways section, turn on the switch next to Apply To All Sidecars.

3. In the Hosts section, click Add Host to add the httpbin service.

4. In the HTTP Route section, click Add Route and configure the parameters as shown in the following figures.

   

   

   

YAML

1. On the Mesh Management page, click the name of the ASM instance. In the left-side navigation pane, choose Traffic Management Center > VirtualService. Click Create from YAML.

2. Paste the following YAML into the code editor and click Create.

   Show the YAML content

   apiVersion: networking.istio.io/v1beta1
   kind: VirtualService
   metadata:
     name: httpbin
     namespace: default
   spec:
     hosts:
       - httpbin.default.svc.cluster.local
     http:
       - match:
           - uri:
               exact: /status/500
         name: error-route
         route:
           - destination:
               host: httpbin.default.svc.cluster.local
       - match:
           - uri:
               prefix: /delay
         name: delay-route
         route:
           - destination:
               host: httpbin.default.svc.cluster.local
       - name: default-route
         route:
           - destination:
               host: httpbin.default.svc.cluster.local

This VirtualService defines three named routes:

Error rate-based circuit breaking

Error rate-based circuit breaking triggers when the server response error rate on a route exceeds a configured threshold within a time window. Use this type when your upstream service returns an elevated rate of 5xx errors.

1. Log on to the ASM console. In the left-side navigation pane, choose Service Mesh > Mesh Management.

2. On the Mesh Management page, click the name of the ASM instance. In the left-side navigation pane, choose Traffic Management Center > Circuit Breaking and Degradation.

3. Click Create, paste the following YAML into the code editor, and click Create.

   Show the YAML content

   apiVersion: istio.alibabacloud.com/v1beta1
   kind: ASMCircuitBreaker
   metadata:
     name: httpbin-error-circuitbreak
     namespace: default
   spec:
     configs:
       - breaker_config:
           break_duration: 60s
           custom_response:
             body: error break!
             header_to_add:
               x-envoy-overload: 'true'
             status_code: 499
           error_percent:
             value: 60
           min_request_amount: 5
           window_size: 10s
         match:
           vhost:
             name: httpbin.default.svc.cluster.local
             port: 8000
             route:
               name_match: error-route
     workloadSelector:
       labels:
         app: sleep

   The following table describes each parameter:

for i in {1..100};  do kubectl exec -it deploy/sleep -- curl httpbin:8000/status/500 -I | grep 'HTTP';  echo ''; sleep 0.1; done;

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 499 Unknown

HTTP/1.1 499 Unknown

HTTP/1.1 499 Unknown

...

for i in {1..100};  do kubectl exec -it deploy/sleep -- curl httpbin:8000/status/503 -I | grep 'HTTP';  echo ''; sleep 0.1; done;

HTTP/1.1 503 Service Unavailable

HTTP/1.1 503 Service Unavailable

HTTP/1.1 503 Service Unavailable

...

Slow request-based circuit breaking

Slow request-based circuit breaking triggers when too many requests take longer than a configured response time threshold within a time window. Use this type when your upstream service experiences latency spikes rather than outright errors.

1. Log on to the ASM console. In the left-side navigation pane, choose Service Mesh > Mesh Management.

2. On the Mesh Management page, click the name of the ASM instance. In the left-side navigation pane, choose Traffic Management Center > Circuit Breaking and Degradation.

3. Click Create, paste the following YAML into the code editor, and click Create.

   Show the YAML content

   apiVersion: istio.alibabacloud.com/v1beta1
   kind: ASMCircuitBreaker
   metadata:
     name: httpbin-error-circuitbreak
     namespace: default
   spec:
     configs:
       - breaker_config:
           break_duration: 60s
           custom_response:
             body: error break!
             header_to_add:
               x-envoy-overload: 'true'
             status_code: 498
           error_percent:
             value: 60
           slow_request_rt: 0.5s
           max_slow_requests: 5
           min_request_amount: 5
           window_size: 10s
         match:
           vhost:
             name: httpbin.default.svc.cluster.local
             port: 8000
             route:
               name_match: delay-route
     workloadSelector:
       labels:
         app: sleep

   The following table describes the parameters specific to slow request-based circuit breaking. For shared parameters (workloadSelector.labels, break_duration, window_size, min_request_amount, custom_response, match.vhost), see the error rate-based parameter reference.

for i in {1..100};  do kubectl exec -it deploy/sleep -- curl httpbin:8000/delay/1 -I | grep 'HTTP';  echo ''; sleep 0.1; done;

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 200 OK

HTTP/1.1 498 Unknown

HTTP/1.1 498 Unknown

HTTP/1.1 498 Unknown

...

for i in {1..100};  do kubectl exec -it deploy/sleep -- curl httpbin:8000/status/500 -I | grep 'HTTP';  echo ''; sleep 0.1; done;

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 500 Internal Server Error

HTTP/1.1 499 Unknown

HTTP/1.1 499 Unknown

HTTP/1.1 499 Unknown

...