You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@servicecomb.apache.org by "Yang Bo (JIRA)" <ji...@apache.org> on 2018/05/16 06:18:00 UTC

[jira] [Updated] (SCB-582) Provide a way to protection for instance removal

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

Yang Bo updated SCB-582:
------------------------
    Fix Version/s: java-chassis-1.0.0-m2

> Provide a way to protection for instance removal
> ------------------------------------------------
>
>                 Key: SCB-582
>                 URL: https://issues.apache.org/jira/browse/SCB-582
>             Project: Apache ServiceComb
>          Issue Type: New Feature
>          Components: Java-Chassis
>            Reporter: liubao
>            Assignee: liubao
>            Priority: Major
>             Fix For: java-chassis-1.0.0-m2
>
>
> In some applications, each microservice have fixed instances and rarely change. But for some reason, heartbeat to service center is not stable. In this scenario, instances will get lost and result in invocation failure. 
>  
> To deal with this problem, we need to provide a way to protect instance removal. That's when there is instance removal, we first check(ping)the instance to see if it is reachable. If it's reachable, we don't remove it. 
>  
> Since this protection is not fit for docker applications or scenarios where instances are constantly removed and added, and resources(hosts ,ip, port) are reused, this feature is an optional feature and users can open it when necessary. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)