[GitHub] [servicecomb-java-chassis] willard-kali opened a new issue #1451: EdgeService熔断配置不生效

[GitBox <gi...@apache.org>]

willard-kali opened a new issue #1451: EdgeService熔断配置不生效
URL: https://github.com/apache/servicecomb-java-chassis/issues/1451
 
 
   EdgeService，
   pom引用了bizkeeper：
   
   > \<dependency>
               \<groupId>org.apache.servicecomb\</groupId>
               \<artifactId>handler-bizkeeper\</artifactId>
               \<version>1.2.1\</version>
           \</dependency>
   
   微服务yaml配置如下：
   > servicecomb:
     handler:
       chain:
         Consumer:
           default: bizkeeper-consumer
         Provider:
           default: bizkeeper-provider
     isolation:
       Consumer:
         timeout:
           enabled: true
         timeoutInMilliseconds: 10
       Provider:
         timeout:
           enabled: true
         timeoutInMilliseconds: 10
     circuitBreaker:
       Consumer:
         enabled: true
         **forceOpen: true**
         sleepWindowInMilliseconds: 15000
         requestVolumeThreshold: 1
       Provider:
         enabled: true
         **forceOpen: true**
         sleepWindowInMilliseconds: 15000
         requestVolumeThreshold: 1
     fallback:
       Consumer:
         enabled: true
       Provider:
         enabled: true
     fallbackpolicy:
       Consumer:
         policy: throwexception
       Provider:
         policy: throwexception
   
   上述配置，consumer和provider分开配置进行测试。
   运行后，EdgeService调用微服务的接口逻辑，直接就报490，表示bizkeeper-consumer生效了，符合预期。
   但是浏览器直接访问EdgeService时，bizkeeper-provider未生效，没有报490。
   **请问在EdgeService这种网关服务上，bizkeeper-provider的熔断策略是否不会生效？**
   
   看了下org.apache.servicecomb.bizkeeper.ProviderBizkeeperHanlder的源码，没看懂它的处理逻辑是什么样子的。

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services