You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@servicecomb.apache.org by "liubao (Jira)" <ji...@apache.org> on 2022/12/29 02:46:00 UTC

[jira] [Resolved] (SCB-2742) change IsolationDiscoveryFilter enabled by false

     [ https://issues.apache.org/jira/browse/SCB-2742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

liubao resolved SCB-2742.
-------------------------
    Resolution: Fixed

> change IsolationDiscoveryFilter enabled by false
> ------------------------------------------------
>
>                 Key: SCB-2742
>                 URL: https://issues.apache.org/jira/browse/SCB-2742
>             Project: Apache ServiceComb
>          Issue Type: Improvement
>          Components: Java-Chassis
>            Reporter: liubao
>            Assignee: liubao
>            Priority: Major
>             Fix For: java-chassis-2.9.0
>
>
> Motivations:
>  
>  # In error condition,  the best choice for protection is fast fail, not ensure the invocation success. In many situations, the way we try to make the invocation success, will cause more problems.
>  # For example, if one instance error goes to 50% or 50% invocations timeout, and we isolate the instance, this will migrate invocations to other instances. In real applications, the migration will cause other instance fail. (Microservice instances are stateless, and one fail , the other may fail. ) 
>  # We suggest users to use instance-isolation-consumer,instance-bulkhead-consumer to make failure fail fast, and not isolation the instance, so that when the window is match, this instance can be available. And we do not migrate the invocations from this instance to others, this will not cause too many invocations to other instances. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)