[
https://issues.apache.org/jira/browse/SCB-582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475859#comment-16475859
]
ASF GitHub Bot commented on SCB-582:
------------------------------------
coveralls commented on issue #704: [SCB-582]Provide a way to protect instance
removal
URL:
https://github.com/apache/incubator-servicecomb-java-chassis/pull/704#issuecomment-389173534
[](https://coveralls.io/builds/16990947)
Coverage increased (+0.02%) to 87.365% when pulling
**6cf01cf7ac0d9a0da5749c2375d5a45309022bbd on liubao68:instance_protection**
into **2f8de349d4b0b82d3dc14fcb9c94d3ae7046f9b5 on apache:master**.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> 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
>
> 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)
