You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by "chickenlj (GitHub)" <gi...@apache.org> on 2020/03/13 10:14:05 UTC

[GitHub] [dubbo] chickenlj commented on issue #5823: Zone-Aware police couldn't work when service instance registered to multi-zone registries

Something is wrong with the picture explaining how it works:

> One provider instance such as B1 should be able to register to multiple registries in the same time.

**One provider only registers to one registry.** So you should have two providers to do the test, with one:

Provider#1
```properties
dubbo.protocol.name=dubbo
dubbo.protocol.port=12345

dubbo.config.multiple=true
dubbo.registry.id=nuc
dubbo.registry.address=nacos://127.0.0.1:8848
dubbo.registry.zone=nuc
dubbo.registry.use-as-config-center=false
```
and another one:

Provider#2
```properties
dubbo.protocol.name=dubbo
dubbo.protocol.port=12345

dubbo.config.multiple=true
dubbo.registry.id=mbp
dubbo.registry.address=nacos://192.168.1.31:8848
dubbo.registry.zone=mbp
dubbo.registry.use-as-config-center=false
```

**It's the Consumer that need to care about all the two registries:**
```properties
server.port=0
## Dubbo Registry
dubbo.registries.a.address=nacos://127.0.0.1:8848?zone=nuc
dubbo.registries.a.zone=nuc
dubbo.registries.a.use-as-config-center=false

dubbo.registries.b.address=nacos://127.0.0.1:8848
dubbo.registries.b.zone=mbp
dubbo.registries.b.use-as-config-center=false
```

[ Full content available at: https://github.com/apache/dubbo/issues/5823 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org