物聯網架構成長之路(55)-Gateway+Sentinel實現限流、熔斷

0. 前言
　　之前有一篇博客講到入門Sentinel，這次就將Sentinel引入到實際項目中進行演示。

1.啟動Sentinel
　　具體可以參考這篇博客
　　https://www.cnblogs.com/wunaozai/p/12404712.html

java -jar sentinel-dashboadr-1.7.1.jar --server.port=8858

　　項目中pom.xml引入

        <dependency>
            <groupId>com.alibaba.cloud</groupId>
            <artifactId>spring-cloud-starter-alibaba-sentinel</artifactId>
        </dependency>
        <dependency>
            <groupId>com.alibaba.csp</groupId>
            <artifactId>sentinel-datasource-nacos</artifactId>
        </dependency>
        <dependency>
            <groupId>com.alibaba.csp</groupId>
            <artifactId>sentinel-transport-simple-http</artifactId>
        </dependency>
        <dependency>
            <groupId>com.alibaba.csp</groupId>
            <artifactId>sentinel-spring-cloud-gateway-adapter</artifactId>
        </dependency>

　　以下配置追加到xxx-story-gateway-dev.properties的配置中，表示集成Sentinel

spring.cloud.sentinel.transport.dashboard=127.0.0.1:8858
spring.cloud.sentinel.datasource.ds.nacos.server-addr=127.0.0.1:8848
spring.cloud.sentinel.datasource.ds.nacos.data-id=gateway-sentinel.properties
spring.cloud.sentinel.datasource.ds.nacos.namespace=0e152861-1efa-62ea-9125-e569abc29691
spring.cloud.sentinel.datasource.ds.nacos.group-id=DEFAULT_GROUP
spring.cloud.sentinel.datasource.ds.nacos.data-type=json
spring.cloud.sentinel.datasource.ds.nacos.rule-type=flow

 

2. 動態修改Nacos上的Sentinel配置

[
    {
        "resource": "/hello",
        "limitApp": "default",
        "grade": 1,
        "count": 5,
        "strategy": 0,
        "controlBehavior": 0,
        "clusterMode": false
    },
    {
        "resource": "/aiml/v1/ai/chat",
        "limitApp": "default",
        "grade": 1,
        "count": 2,
        "strategy": 0,
        "controlBehavior": 0,
        "clusterMode": false
    }
]

 

3. 配置Sentinel Configuration
　　在對流量進行限流和熔斷過程中，需要一些自定義操作。此時就需要增加一個GatewayConfiguration配置類。因為默認提示異常是【Blocked by Sentinel: FlowException】，所以最好是能，自定義異常提示。
　　GatewayConfiguration.java

package com.wunaozai.demo.story.gateway.config;

import java.util.Collections;
import java.util.List;

import org.springframework.beans.factory.ObjectProvider;
import org.springframework.cloud.gateway.filter.GlobalFilter;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.core.Ordered;
import org.springframework.core.annotation.Order;
import org.springframework.http.codec.ServerCodecConfigurer;
import org.springframework.web.reactive.result.view.ViewResolver;

import com.alibaba.csp.sentinel.adapter.gateway.sc.SentinelGatewayFilter;

@Configuration
public class GatewayConfiguration {

    private final List<ViewResolver> views;
    private final ServerCodecConfigurer configurer;
    
    public GatewayConfiguration(ObjectProvider<List<ViewResolver>> views,
            ServerCodecConfigurer config) {
        this.views = views.getIfAvailable(Collections::emptyList);
        this.configurer = config;
    }
    
    /**
     * 配置SentinelGatewayBlockExceptionHandler，限流后異常處理
     * @return
     */
    @Bean
    @Order(Ordered.HIGHEST_PRECEDENCE)
    public JsonSentinelGatewayBlockExceptionHandler sentinelGatewayBlockExceptionHandler() {
        //return new SentinelGatewayBlockExceptionHandler(views, configurer);
        return new JsonSentinelGatewayBlockExceptionHandler(views, configurer);
    }
    
    /**
     * Sentinel 過濾器
     * @return
     */
    @Bean
    @Order(-1)
    public GlobalFilter sentinelGatewayFilter() {
        return new SentinelGatewayFilter();
    }
    
}

　　JsonSentinelGatewayBlockExceptionHandler.java

package com.wunaozai.demo.story.gateway.config;

import java.nio.charset.StandardCharsets;
import java.util.List;

import org.springframework.core.io.buffer.DataBuffer;
import org.springframework.http.codec.HttpMessageWriter;
import org.springframework.http.codec.ServerCodecConfigurer;
import org.springframework.http.server.reactive.ServerHttpResponse;
import org.springframework.web.reactive.function.server.ServerResponse;
import org.springframework.web.reactive.result.view.ViewResolver;
import org.springframework.web.server.ServerWebExchange;
import org.springframework.web.server.WebExceptionHandler;

import com.alibaba.csp.sentinel.adapter.gateway.sc.callback.GatewayCallbackManager;
import com.alibaba.csp.sentinel.slots.block.BlockException;
import com.alibaba.csp.sentinel.util.function.Supplier;

import reactor.core.publisher.Mono;

/**
 * Sentinel 限流后自定義異常
 * @author wunaozai
 * @Date 2020-03-17
 */
public class JsonSentinelGatewayBlockExceptionHandler implements WebExceptionHandler {

    private List<ViewResolver> viewResolvers;
    private List<HttpMessageWriter<?>> messageWriters;

    public JsonSentinelGatewayBlockExceptionHandler(
            List<ViewResolver> viewResolvers, ServerCodecConfigurer serverCodecConfigurer) {
        this.viewResolvers = viewResolvers;
        this.messageWriters = serverCodecConfigurer.getWriters();
    }
    /**
     * 自定義返回
     * @param response
     * @param exchange
     * @return
     */
    private Mono<Void> writeResponse(ServerResponse response, ServerWebExchange exchange) {
        ServerHttpResponse resp = exchange.getResponse();
        resp.getHeaders().add("Content-Type", "application/json;charset=UTF-8");
        String json = "{\"code\": -1, \"data\": null, \"msg\": \"系統限流\"}";
        DataBuffer buffer = resp.bufferFactory().wrap(json.getBytes(StandardCharsets.UTF_8));
        return resp.writeWith(Mono.just(buffer));
    }

    @Override
    public Mono<Void> handle(ServerWebExchange exchange, Throwable ex) {
        if (exchange.getResponse().isCommitted()) {
            return Mono.error(ex);
        }
        if (!BlockException.isBlockException(ex)) {
            return Mono.error(ex);
        }
        return handleBlockedRequest(exchange, ex)
            .flatMap(response -> writeResponse(response, exchange));
    }
    private Mono<ServerResponse> handleBlockedRequest(ServerWebExchange exchange, Throwable throwable) {
        return GatewayCallbackManager.getBlockHandler().handleRequest(exchange, throwable);
    }
    private final Supplier<ServerResponse.Context> contextSupplier = () -> new ServerResponse.Context() {
        @Override
        public List<HttpMessageWriter<?>> messageWriters() {
            return JsonSentinelGatewayBlockExceptionHandler.this.messageWriters;
        }
        @Override
        public List<ViewResolver> viewResolvers() {
            return JsonSentinelGatewayBlockExceptionHandler.this.viewResolvers;
        }
    };
}

 

 

4. 熔斷機制
　　上面介紹的是限流，可以從 spring.cloud.sentinel.datasource.ds.nacos.rule-type=flow 看出來。但是根據 org.springframework.cloud.alibaba.sentinel.datasource.RuleType 這個枚舉，Sentinel還提供了熔斷機制。

　　修改之前的配置，增加多一個數據源，一個是限流，一個是熔斷

#Sentinel
spring.cloud.sentinel.transport.dashboard=127.0.0.1:8858
spring.cloud.sentinel.datasource.ds1.nacos.server-addr=127.0.0.1:8848
spring.cloud.sentinel.datasource.ds1.nacos.data-id=gateway-sentinel.properties
spring.cloud.sentinel.datasource.ds1.nacos.namespace=0e152861-1efa-62ea-9125-e569abc29691
spring.cloud.sentinel.datasource.ds1.nacos.group-id=DEFAULT_GROUP
spring.cloud.sentinel.datasource.ds1.nacos.data-type=json
spring.cloud.sentinel.datasource.ds1.nacos.rule-type=flow

spring.cloud.sentinel.datasource.ds2.nacos.server-addr=127.0.0.1:8848
spring.cloud.sentinel.datasource.ds2.nacos.data-id=gateway-sentinel-degrade.properties
spring.cloud.sentinel.datasource.ds2.nacos.namespace=0e152861-1efa-62ea-9125-e569abc29691
spring.cloud.sentinel.datasource.ds2.nacos.group-id=DEFAULT_GROUP
spring.cloud.sentinel.datasource.ds2.nacos.data-type=json
spring.cloud.sentinel.datasource.ds2.nacos.rule-type=degrade

　　這個配置的意思是，如果請求xxx-story-res這個微服務是，當資源的平均響應時間超過閾值100ms后，資源進入准降級狀態。如果接下來1秒內持續進入多個請求的RT時間都持續超過這個閾值，那么在接下來的時間窗口（timeWindow）30（秒）之內。對該方法的調用都會自動熔斷。直接返回錯誤。這里會直接返回上面配置的 {"code": -1, "data": null, "msg": "系統限流"} 錯誤。

[
  {
    "resource": "xxx-story-res",
    "count": 100,
    "grade": 0,
    "timeWindow": 30
  }
]

　　現在測試，就是不斷的請求對應的接口，從圖中可以看到，每隔30秒，就會放一些請求到后面的服務。其他時間的請求，都是快速失敗。返回限流。

 

5. 附錄各個在Nacos上的配置 

 

參考資料：
　　https://github.com/alibaba/Sentinel/wiki/%E7%83%AD%E7%82%B9%E5%8F%82%E6%95%B0%E9%99%90%E6%B5%81
　　https://www.cnblogs.com/yinjihuan/p/10772558.html
　　https://www.cnblogs.com/zhangpan1244/p/11228020.html

本文地址：https://www.cnblogs.com/wunaozai/p/12512850.html
本系列目錄： https://www.cnblogs.com/wunaozai/p/8067577.html
個人主頁：https://www.wunaozai.com/