【sentinel】深入浅出之原理篇集群流控之Demo

关于集群限流的功能,官方文档写的非常详细:集群流控官方文档
官方文档中有demo,但是隐藏了太多细节,且依赖了nacos,我这里自己写了一个demo。

demo地址: https://github.com/shxz130/sentinel-demo
首先启动一个Server端:

  • 设置FlowRule,并将其设置为Cluster模式
  • 初始化Server(Client和Server都可以共用)
  • 初始化Client,指定Server端地址。
  • 将该节点设置为Server 端,并启动。
 public static void main(String[] args) {
    //初始化限流规则
    initClusterFlowRule();
    //初始化Server
    initServer();
    //初始化Cluster Client规则,指定Server ip和端口
    initClusterClientRule();
    //设置为Server 并启动
    setToServer();
    while (true){
        //等待10秒
        try{
            Thread.sleep(100);
        }catch (Exception e){
            e.printStackTrace();
        }
        try{
            //对资源A限流
            Entry entry=SphU.entry("a");
            System.out.println("pass");
        }catch (Exception e){
            System.out.println("block");
        }
    }
}

在初始化规则的时候,指定集群 or 单机模式,指定限流规则,指定限流类型qps or threads ,最后,加载单机规则,集群NameSpace以及nameSpace对应的集群规则。

private static void initClusterFlowRule(){
   List<FlowRule> flowRules=new ArrayList<FlowRule>();
   FlowRule flowRule=new FlowRule();
   //指定限流规则的Resource
   flowRule.setResource("a");
   //集群限流规则配置
   ClusterFlowConfig clusterFlowConfig=new ClusterFlowConfig();
   //集群失效是否转移
   clusterFlowConfig.setFallbackToLocalWhenFail(true);
   //指定flowId 可以使用IP+进程号区分
   clusterFlowConfig.setFlowId(1L);
   //限流规则 全局总数或者平均分摊
   clusterFlowConfig.setThresholdType(ClusterRuleConstant.FLOW_THRESHOLD_GLOBAL);
   flowRule.setClusterConfig(clusterFlowConfig);
   //是否启用Cluster模式
   flowRule.setClusterMode(true);
   //默认限流规则,具体可以看FlowSlot介绍
   flowRule.setControlBehavior(RuleConstant.CONTROL_BEHAVIOR_DEFAULT);
   //总数
   flowRule.setCount(10);
   //策略
   flowRule.setStrategy(RuleConstant.STRATEGY_DIRECT);
   //限制QPS 也可以指定为线程数
   flowRule.setGrade(RuleConstant.FLOW_GRADE_QPS);
   flowRules.add(flowRule);
   //加载配置
   FlowRuleManager.loadRules(flowRules);
   //注册NameSpace
   ClusterFlowRuleManager.registerPropertyIfAbsent("1-name");
   //NameSpace 下面的规则加载到集群模式
   ClusterFlowRuleManager.loadRules("1-name", flowRules);
}

在初始化Server的时候,指定TokenServer的Ip和端口,并加载nameSpace信息到Cluster。

private static void initServer(){
    //指定提供TokenService的端口和地址
    ServerTransportConfig ServerTransportConfig=new ServerTransportConfig(18730,600);
    //加载配置
    ClusterServerConfigManager.loadGlobalTransportConfig(ServerTransportConfig);
    Set<String> nameSpaceSet=new HashSet<String>();
    nameSpaceSet.add("1-name");
    //服务配置namespace
    ClusterServerConfigManager.loadServerNamespaceSet(nameSpaceSet);
    //ClusterServerConfigManager.loadGlobalFlowConfig();
    //配置了nameSpace对应的ServerFlowConfig
}

初始化客户端的时候,实质是指定客户端规则,配置服务端地址和IP。

private static void initClusterClientRule(){
    //初始化客户端规则
    ClusterClientConfig clusterClientConfig = new ClusterClientConfig();
    //指定获取Token超时时间
    clusterClientConfig.setRequestTimeout(1000);
    //Client指定配置
    ClusterClientConfigManager.applyNewConfig(clusterClientConfig);
    //指定TokenServer的Ip和地址
    ClusterClientAssignConfig clusterClientAssignConfig=new ClusterClientAssignConfig("127.0.0.1",18730);
    //应用
    ClusterClientConfigManager.applyNewAssignConfig(clusterClientAssignConfig);
}

最后,启动服务,则是将上面配置的Server信息对外暴漏服务。

private static void setToServer(){
        ClusterStateManager.setToServer();
}

这里的端口号是设置服务端的端口号,单独启动Server,这里配置1s中10个QPS,模拟1s中10个请求,能看到运行结果如下:

Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:24 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass
Fri Mar 22 17:41:25 CST 2019 pass

结果都是通过的,但并不代表限流生效。将1s中请求10个改为20,也就是超时时间由100改为50,运行结果一半通过,一半阻塞

Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:10 CST 2019 pass
Fri Mar 22 17:44:10 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 block
Fri Mar 22 17:44:11 CST 2019 pass
Fri Mar 22 17:44:11 CST 2019 block

可以看到,单机限流是生效了。
为了模拟集群环境,启动一个客户端,客户端的配置和服务端区别在于最后启动的不是Server,而是Client。

public static void main(String[] args) {
    initClusterFlowRule();
    initServer();
    initClusterClientRule();
    //设置为客户端
    setToClient();
    while (true){
        try{
            Thread.sleep(100);
        }catch (Exception e){
            e.printStackTrace();
        }
        try{
            Entry entry=SphU.entry("a");
            System.out.println("pass");
        }catch (Exception e){
            System.out.println("block");
        }
    }
}

设置客户端方式和服务端一致。

private static void setToClient(){
    //设置为客户端
    ClusterStateManager.setToClient();
}

先启动服务端。后启动客户端,可以看到服务端日志:

Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:23 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:24 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:25 CST 2019 pass
三月 22, 2019 5:50:25 下午 io.netty.handler.logging.LoggingHandler channelRead
信息: [id: 0xa7c7acc4, L:/0:0:0:0:0:0:0:0:18730] READ: [id: 0x4338a7c7, L:/127.0.0.1:18730 - R:/127.0.0.1:56654]
三月 22, 2019 5:50:25 下午 io.netty.bootstrap.AbstractBootstrap setChannelOption
警告: Unknown channel option 'SO_TIMEOUT' for channel '[id: 0x4338a7c7, L:/127.0.0.1:18730 - R:/127.0.0.1:56654]'
三月 22, 2019 5:50:25 下午 io.netty.handler.logging.LoggingHandler channelReadComplete
信息: [id: 0xa7c7acc4, L:/0:0:0:0:0:0:0:0:18730] READ COMPLETE
Fri Mar 22 17:50:25 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 pass
Fri Mar 22 17:50:30 CST 2019 block
Fri Mar 22 17:50:30 CST 2019 block
Fri Mar 22 17:50:30 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:31 CST 2019 block
Fri Mar 22 17:50:32 CST 2019 block
Fri Mar 22 17:50:32 CST 2019 pass
Fri Mar 22 17:50:32 CST 2019 pass
Fri Mar 22 17:50:32 CST 2019 pass
Fri Mar 22 17:50:32 CST 2019 pass
Fri Mar 22 17:50:32 CST 2019 pass
Fri Mar 22 17:50:32 CST 2019 pass
Fri Mar 22 17:50:32 CST 2019 block
Fri Mar 22 17:50:32 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 block
Fri Mar 22 17:50:33 CST 2019 pass
Fri Mar 22 17:50:34 CST 2019 pass
Fri Mar 22 17:50:34 CST 2019 pass
Fri Mar 22 17:50:34 CST 2019 pass
Fri Mar 22 17:50:34 CST 2019 pass
Fri Mar 22 17:50:34 CST 2019 block

可以看到,当服务端启动的时候,只有服务端一个节点,所以请求全部通过,当客户端联通服务端之后,因为有了客户端连接,所以服务端有block的请求了。
再看一下客户端的日志:

Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 pass
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:26 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 block
Fri Mar 22 17:50:27 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 pass
Fri Mar 22 17:50:28 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 pass
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:29 CST 2019 block
Fri Mar 22 17:50:30 CST 2019 block
Fri Mar 22 17:50:30 CST 2019 block
Fri Mar 22 17:50:30 CST 2019 block
Fri Mar 22 17:50:30 CST 2019 block

可以看到,在同1s的时间里,客户端和服务端的请求通过数加起来就是集群QPS数。

27s 时 客户端pass1 服务端pass9
28s 时 客户端pass1 服务端pass9
29s 时 客户端pass8 服务端pass2

集群限流生效。

最后编辑于
©著作权归作者所有,转载或内容合作请联系作者
  • 序言:七十年代末,一起剥皮案震惊了整个滨河市,随后出现的几起案子,更是在滨河造成了极大的恐慌,老刑警刘岩,带你破解...
    沈念sama阅读 217,277评论 6 503
  • 序言:滨河连续发生了三起死亡事件,死亡现场离奇诡异,居然都是意外死亡,警方通过查阅死者的电脑和手机,发现死者居然都...
    沈念sama阅读 92,689评论 3 393
  • 文/潘晓璐 我一进店门,熙熙楼的掌柜王于贵愁眉苦脸地迎上来,“玉大人,你说我怎么就摊上这事。” “怎么了?”我有些...
    开封第一讲书人阅读 163,624评论 0 353
  • 文/不坏的土叔 我叫张陵,是天一观的道长。 经常有香客问我,道长,这世上最难降的妖魔是什么? 我笑而不...
    开封第一讲书人阅读 58,356评论 1 293
  • 正文 为了忘掉前任,我火速办了婚礼,结果婚礼上,老公的妹妹穿的比我还像新娘。我一直安慰自己,他们只是感情好,可当我...
    茶点故事阅读 67,402评论 6 392
  • 文/花漫 我一把揭开白布。 她就那样静静地躺着,像睡着了一般。 火红的嫁衣衬着肌肤如雪。 梳的纹丝不乱的头发上,一...
    开封第一讲书人阅读 51,292评论 1 301
  • 那天,我揣着相机与录音,去河边找鬼。 笑死,一个胖子当着我的面吹牛,可吹牛的内容都是我干的。 我是一名探鬼主播,决...
    沈念sama阅读 40,135评论 3 418
  • 文/苍兰香墨 我猛地睁开眼,长吁一口气:“原来是场噩梦啊……” “哼!你这毒妇竟也来了?” 一声冷哼从身侧响起,我...
    开封第一讲书人阅读 38,992评论 0 275
  • 序言:老挝万荣一对情侣失踪,失踪者是张志新(化名)和其女友刘颖,没想到半个月后,有当地人在树林里发现了一具尸体,经...
    沈念sama阅读 45,429评论 1 314
  • 正文 独居荒郊野岭守林人离奇死亡,尸身上长有42处带血的脓包…… 初始之章·张勋 以下内容为张勋视角 年9月15日...
    茶点故事阅读 37,636评论 3 334
  • 正文 我和宋清朗相恋三年,在试婚纱的时候发现自己被绿了。 大学时的朋友给我发了我未婚夫和他白月光在一起吃饭的照片。...
    茶点故事阅读 39,785评论 1 348
  • 序言:一个原本活蹦乱跳的男人离奇死亡,死状恐怖,灵堂内的尸体忽然破棺而出,到底是诈尸还是另有隐情,我是刑警宁泽,带...
    沈念sama阅读 35,492评论 5 345
  • 正文 年R本政府宣布,位于F岛的核电站,受9级特大地震影响,放射性物质发生泄漏。R本人自食恶果不足惜,却给世界环境...
    茶点故事阅读 41,092评论 3 328
  • 文/蒙蒙 一、第九天 我趴在偏房一处隐蔽的房顶上张望。 院中可真热闹,春花似锦、人声如沸。这庄子的主人今日做“春日...
    开封第一讲书人阅读 31,723评论 0 22
  • 文/苍兰香墨 我抬头看了看天上的太阳。三九已至,却和暖如春,着一层夹袄步出监牢的瞬间,已是汗流浃背。 一阵脚步声响...
    开封第一讲书人阅读 32,858评论 1 269
  • 我被黑心中介骗来泰国打工, 没想到刚下飞机就差点儿被人妖公主榨干…… 1. 我叫王不留,地道东北人。 一个月前我还...
    沈念sama阅读 47,891评论 2 370
  • 正文 我出身青楼,却偏偏与公主长得像,于是被迫代替她去往敌国和亲。 传闻我的和亲对象是个残疾皇子,可洞房花烛夜当晚...
    茶点故事阅读 44,713评论 2 354

推荐阅读更多精彩内容

  • 逅弈 转载请注明原创出处,谢谢! 系列文章 Sentinel 原理-全解析Sentinel 原理-调用链Senti...
    逅弈阅读 38,543评论 5 34
  • ORA-00001: 违反唯一约束条件 (.) 错误说明:当在唯一索引所对应的列上键入重复值时,会触发此异常。 O...
    我想起个好名字阅读 5,311评论 0 9
  • 2019已经悄然而至,依然记得2017年末自己对2018年的许诺:成为顾问妈妈。但总以陪伴小宝为借口,生活没有任何...
    瑞丞妈妈阅读 118评论 0 0
  • #一起成长读书会张利锋阅读分享第五天# 金句 1. 只有做自己热爱的事情,你才会有真正的成就感。不要把金钱当成你的...
    张利锋阅读 104评论 0 0