@toc

Source code address ：gitee Code warehouse address

1、 Why would you Sentienl Rule persistence ？

   Once we restart the app ,sentinel The rules will disappear , The production environment needs to persist the configuration rules

2、 The idea of persistence

   We will now persist the current limiting configuration rule into Nacos preservation , Just refresh 8401 Some rest Address ,sentinel You can see the flow control rules of the console , as long as Nacos The configuration is not deleted , in the light of 8401 On sentinel The flow control rules on the Internet remain valid .

3、 Operation steps

3.1 Introducing dependencies into a project

<!--SpringCloud ailibaba sentinel-datasource-nacos --><dependency>    <groupId>com.alibaba.csp</groupId>    <artifactId>sentinel-datasource-nacos</artifactId></dependency>

3.2 add to Nacos Data source configuration

application.yml

server:  port: 8401spring:  application:    name: cloudalibaba-sentinel-service  cloud:    nacos:      discovery:        #Nacos Address of service registration center         server-addr: localhost:8848    sentinel:      transport:        # To configure Sentinel dashboard Address         dashboard: localhost:8080        # Default 8719 port , If it is occupied, it will be automatically transferred from 8719 Start in sequence +1 scanning , Until the unoccupied port is found         port: 8719      datasource:        ds1:  # add to nacos Configuration of data source , take sentinel Configure persistence nacos Inside           nacos:            server-addr: localhost:8848            dataId: cloudalibaba-sentinel-service            groupId: DEFAULT_GROUP            data-type: json            rule-type: flowmanagement:  endpoints:    web:      exposure:        include: '*'

3.3 add to Nacos Business rule configuration

[    {        "resource": "/rateLimit/byUrl",        "limitApp": "default",        "grade": 1,        "count": 1,        "strategy": 0,        "controlBehavior": 0,        "clusterMode": false    }]

resource： Resource name ;
limitApp： Source application ;
grade： Threshold type ,0 Number of threads ,1 Express QPS;
count： Stand alone threshold ;
strategy： Flow control mode ,0 It means direct ,1 Express Association ,2 Represents a link ;
controlBehavior： Flow control effect ,0 Express a quick failure ,1 Express Warm Up,2 Stand in line ;
clusterMode： Cluster or not .

3.4 start-up sentinel

3.5 Start at this time 8401 Micro service and refresh Sentinel

   Found that the business rules have .

  nacos above ：

  sentinel above ：

3.6 test

   What we configured above means , This interface can only handle 1 A request , Then we frequently refresh requests , See if the current limit rules are in effect .

   Normal access first ：http://localhost:8401/rateLimit/byUrl

   Frequent visits ：http://localhost:8401/rateLimit/byUrl

   You can see , Triggered the current limit rule . Here we do not specify in the program blockHandler, Therefore, the information after the default current limit is displayed .

3.7 stop it 8401 Micro service view

   stop it 8401 It is found that the flow control rules are gone .

3.8 restart 8401 Look at microservices again sentinel

   Or not? , Let's visit once http://localhost:8401/rateLimit/byUrl, Refresh again Sentinel

   Configuration error , Persistence validation passed .