You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2019/01/20 04:25:04 UTC

[GitHub] joooohnli edited a comment on issue #1773: Get exceptions while config refreshed through Orchestration

joooohnli edited a comment on issue #1773: Get exceptions while config refreshed  through Orchestration
URL: https://github.com/apache/incubator-shardingsphere/issues/1773#issuecomment-455836382
 
 
   @tristaZero 
   Not really, those exceptions are threw one by one under the exactly same situation (check the log time).
   
   And B instance is always running there, it's configuration get refreshed automatically since it subscribed the ZK. 
   Configuration of instance B:
   ```
   sharding.jdbc.config.orchestration.name= za_blacklist
   sharding.jdbc.config.orchestration.overwrite=false
   sharding.jdbc.config.orchestration.registry.namespace=sharding-jdbc-business
   sharding.jdbc.config.orchestration.registry.server-lists=xx:2181
   ```

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services