dubbo

1.回声测试发生在调用端 通过filter直接返回，不涉及rpc过程

2.失败重拾默认3次，超时时间默认1s

3.容错配置 consumer优先适用 

4.线程池打满：

cause: Server side(192.168.1.103,20880) threadpool is exhausted ,detail msg:Thread pool is EXHAUSTED! Thread Name: DubboServerHandler-192.168.1.103:20880, Pool Size: 2 (active: 2, core: 2, max: 2, largest: 2), Task: 21 (completed: 19), Executor status:(isShutdown:false, isTerminated:false, isTerminating:false), in dubbo://192.168.1.103:20880!
at com.alibaba.dubbo.rpc.cluster.support.FailoverClusterInvoker.doInvoke(FailoverClusterInvoker.java:101)

5.默认fixed线程池

6.每种暴露协议对应一个url：

rmi://192.168.1.103:20882/com.personal.service.IDubboTest?anyhost=true&application=api-test&dubbo=2.6.0&generic=false&group=test&interface=com.personal.service.IDubboTest&methods=dubboTest,loadBanlance&pid=34337&retries=5&side=provider&timestamp=1590593662996,

dubbo://192.168.1.103:20881/com.personal.service.IDubboTest?anyhost=true&application=api-test&dubbo=2.6.0&generic=false&group=test&interface=com.personal.service.IDubboTest&methods=dubboTest,loadBanlance&pid=34337&retries=5&side=provider&timestamp=1590593663328

7.动态降级的时候 向configurators节点写入：

 8.accesslog长这个样子：

 

 9.当我们设置failover retries=0时会发现还是会重试2次，观察这个时候的url：

 

 

consumer://192.168.1.103/com.personal.service.RedisOpsService?application=api-test&category=consumers&check=false&cluster=failover&dubbo=2.6.0&interface=com.personal.service.RedisOpsService&methods=subscribe&pid=16222&side=consumer&timestamp=1591291208928

发现并没有retries的设置，0被认为是默认值 未设置的配置，再采用failover的时候就会用默认值2 导致重试2 次