[
https://issues.apache.org/jira/browse/SCB-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin updated SCB-1083:
-------------------------
Description:
1.when deploy or upgrade, microservice instance will start with status:
TESTING, all consumers will not invoke this instance
2.test tool will invoke the instance with special ip, after test finished
successfully, test tool will change the instance status to UP, all consumers
can invoke this instance now.
3.this instance will publish a event with old instance and new instance, to let
business logic know: my instance changed.
tasks:
* SC add a status: TESTING (already finished)
* SC add batch pull instances api, and supoort pull special instance in this
api (already finished)
* SDK allow control status from configuration
* SDK change loop pull all target microservice instance to batch pull, and
pull self instance, when self instance changed, publish a new event
incompatible:
{code:java}
RegistryUtils.getServiceRegistry()
.getAppManager()
.getOrCreateMicroserviceVersionRule(......)
.getVersionedCache()
{code}
old version: only return instances which status is UP
new version: return all instances
was:
1.when deploy or upgrade, microservice instance will start with status:
TESTING, all consumers will not invoke this instance
2.test tool will invoke the instance with special ip, after test finished
successfully, test tool will change the instance status to UP, all consumers
can invoke this instance now.
3.this instance will publish a event with old instance and new instance, to let
business logic know: my instance changed.
tasks:
* SC add a status: TESTING (already finished)
* SC add batch pull instances api, and supoort pull special instance in this
api (already finished)
* SDK allow control status from configuration
* SDK change loop pull all target microservice instance to batch pull, and
pull self instance, when self instance changed, publish a new event
> support test before provide service
> -----------------------------------
>
> Key: SCB-1083
> URL: https://issues.apache.org/jira/browse/SCB-1083
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
> Reporter: wujimin
> Assignee: liubao
> Priority: Major
> Labels: incompatibleChange
> Fix For: java-chassis-1.2.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 1.when deploy or upgrade, microservice instance will start with status:
> TESTING, all consumers will not invoke this instance
> 2.test tool will invoke the instance with special ip, after test finished
> successfully, test tool will change the instance status to UP, all consumers
> can invoke this instance now.
> 3.this instance will publish a event with old instance and new instance, to
> let business logic know: my instance changed.
>
> tasks:
> * SC add a status: TESTING (already finished)
> * SC add batch pull instances api, and supoort pull special instance in
> this api (already finished)
> * SDK allow control status from configuration
> * SDK change loop pull all target microservice instance to batch pull, and
> pull self instance, when self instance changed, publish a new event
>
> incompatible:
> {code:java}
> RegistryUtils.getServiceRegistry()
> .getAppManager()
> .getOrCreateMicroserviceVersionRule(......)
> .getVersionedCache()
> {code}
> old version: only return instances which status is UP
> new version: return all instances
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
