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

Jimin Wu updated SCB-2217:
--------------------------
    Description: 
1. configuration sample
{code:yaml}
servicecomb:  
  service:  
    zero-config:  
      enabled: true  
      address: 0.0.0.0:6666  
      group: 225.6.7.8  
{code}
2. All instances can be discovered regardless of the order in which they are 
started

3. reject instance register, when schema changed, but version not changed, and 
has existing instances

4. allow register instance, when schema changed, and version not changed, but 
has not existing instances
 and consumers will clear related microservice, build them when next related 
invocation start

5. fix some revision of pull instances, (not fix all)

  was:
1. configuration sample

{code:yaml}
servicecomb:  
  service:  
    zero-config:  
      enabled: true  
      address: 0.0.0.0:6666  
      group: 225.6.7.8  
{code}

2. All instances can be discovered regardless of the order in which they are 
started

3. reject instance register, when schema changed, but version not changed, and 
has existing instances

4. allow register instance, when schema changed, and version not changed, but 
has not existing instances
    and consumers will clear related microservice, build them when next related 
invocation start


> [temp-solution] make zero-config workable
> -----------------------------------------
>
>                 Key: SCB-2217
>                 URL: https://issues.apache.org/jira/browse/SCB-2217
>             Project: Apache ServiceComb
>          Issue Type: Improvement
>          Components: Java-Chassis
>            Reporter: Jimin Wu
>            Assignee: Jimin Wu
>            Priority: Major
>             Fix For: java-chassis-2.3.0
>
>
> 1. configuration sample
> {code:yaml}
> servicecomb:  
>   service:  
>     zero-config:  
>       enabled: true  
>       address: 0.0.0.0:6666  
>       group: 225.6.7.8  
> {code}
> 2. All instances can be discovered regardless of the order in which they are 
> started
> 3. reject instance register, when schema changed, but version not changed, 
> and has existing instances
> 4. allow register instance, when schema changed, and version not changed, but 
> has not existing instances
>  and consumers will clear related microservice, build them when next related 
> invocation start
> 5. fix some revision of pull instances, (not fix all)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to