将限流规则持久化到nacos中:8401项目演示:
项目需要的
(1)pom:
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<parent>
<artifactId>com.fan.springcloud</artifactId>
<groupId>org.example</groupId>
<version>1.0-SNAPSHOT</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>cloudalibaba-sentinel-service8401</artifactId>
<dependencies>
<!---alibaba-nacos-discovery-->
<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
</dependency>
<!--sentinel-datasource-nacos-->
<dependency>
<groupId>com.alibaba.csp</groupId>
<artifactId>sentinel-datasource-nacos</artifactId>
</dependency>
<!--alibaba-sentinel-->
<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-starter-alibaba-sentinel</artifactId>
</dependency>
<!--openfeign-->
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-openfeign</artifactId>
</dependency>
<!--spring-boot-starter-web-->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
</dependency>
<!--spring-boot-starter-actuator-->
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-actuator</artifactId>
</dependency>
<dependency><!--热部署-->
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-devtools</artifactId>
<scope>runtime</scope>
<optional>true</optional>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<optional>true</optional>
</dependency>
<dependency>
<groupId>cn.hutool</groupId>
<artifactId>hutool-core</artifactId>
<version>5.6.5</version>
</dependency>
</dependencies>
</project>
(2)yml:
server:
port: 8401
spring:
application:
name: cloudalibaba-sentinel-service
cloud:
nacos:
discovery:
#nacos服务注册中心地址,这里我们使用了nginx做了均衡负载
server-addr: 192.168.211.205:1111
sentinel:
transport:
#配置sentinel 仪表盘地址
dashboard: localhost:8080
#默认8719端口,假如被占用会自动从8719开始依次+1扫描找端口
port: 8719
datasource:
ds1:
nacos:
server-addr: 192.168.211.205:1111
dataId: cloudalibaba-sentinel-service
groudId: DEFAULT_GROUP
data-type: json
rule-type: flow
management:
endpoints:
web:
exposure:
include: '*'
(3)nacos流控规则的配置:
使用http://192.168.211.205:8848/nacos/ 进入nacos控制台:
nacos控制台新建流控配置:
[
{
"resource": "/rateLimit/byUrl",
"limitApp": "default",
"grade": 1,
"count": 1,
"strategy": 0,
"controlBebavior": 0,
"clusterMode": false
}
]
配置说明:
resource: 资源名称
limitApp: 来源应用
grade: 阈值类型,0表示线程,1表示QPS
count: 单机阈值
strategy: 流控模式,0表示直接,1表示关联,2表示链路
controlBehavior: 流控效果,0表示快速失败,1表示Warm Up,2表示排队等待
clusterMode: 是否集群
配置多个规则:
[
{
"resource": "myBlockHandler",
"limitApp": "default",
"grade": "1",
"count": "1",
"strategy": "0",
"controlBehavior": "0",
"clusterMode": false
},
{
"resource": "flowLimit",
"limitApp": "default",
"grade": "1",
"count": "1",
"strategy": "0",
"controlBehavior": "0",
"clusterMode": false
}
]
Nacos配置文件发布后,会马上在Sentinel更新。
当我们在那边的nacos配置的一个新流控规则的配置,则可以启动服务,并在sentinel控制台看到配置好的流控规则:
(4)主启动类:
package com.fan.springcloud;
import org.springframework.boot.SpringApplication;
import org.springframework.boot.autoconfigure.SpringBootApplication;
import org.springframework.cloud.client.discovery.EnableDiscoveryClient;
@SpringBootApplication
@EnableDiscoveryClient
public class SentinelMainApp8401 {
public static void main(String[] args) {
SpringApplication.run(SentinelMainApp8401.class,args);
}
}
(5)controller:
package com.fan.springcloud.controller;
import com.alibaba.csp.sentinel.annotation.SentinelResource;
import com.alibaba.csp.sentinel.slots.block.BlockException;
import com.fan.springcloud.myhandler.CustomerBlockHandler;
import org.springframework.web.bind.annotation.GetMapping;
import org.springframework.web.bind.annotation.RestController;
@RestController
public class RateLimitcontroller {
//按照资源名称限流
@GetMapping("/byResource")
@SentinelResource(value = "byResource" ,
blockHandler = "handlerException")
public String byResource(){
return "code:200,message:按照资源名称限流测试";
}
//兜底的方法
public String handlerException(BlockException exception){
return "code:4444,message:"+exception.getClass().getCanonicalName()+
"\t 服务不可用";
}
//按照Url地址限流
@GetMapping("/rateLimit/byUrl")
@SentinelResource(value = "byUrl")
public String byUrl(){
return "code:200,message:按照Url地址限流测试ok";
}
//客户自定义限流
@GetMapping("/rateLimit/customerBlockHandler")
@SentinelResource(value = "customerBlockHandler",
blockHandlerClass = CustomerBlockHandler.class,
blockHandler = "handlerException2")
public String customerBlockHandler(){
return "code:200,message:按照客户自定义限流测试ok";
}
}
(6)快速访问测试接口:localhost:8401/rateLimit/byUrl
多次点击出现限流:
(7)停止8401后看sentinel:发现流控规则没有了
sentinel是懒加载机制,只有当服务发起了请求,控制台才能看到并进行操作。
重新启动8401服务后并多次调用:http://localhost:8401/rateLimit/byUrl
发现sentinel出现流控规再次出现,如下: