HaoLi-Rainbow opened a new issue #9306:
URL: https://github.com/apache/dubbo/issues/9306


   问题:
   
   dubbo使用nacos的配置中心之后会疯狂往配置中心写入配置, 我们一共就8个项目, dubbo写入的配置文件就写了50个, 这个正常吗?
   
   
   使用版本
   
   ```xml
           <dependency>
               <groupId>com.alibaba.cloud</groupId>
               
<artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId>
               <version>2.2.2.RELEASE</version>
           </dependency>
           <dependency>
               <groupId>com.alibaba.cloud</groupId>
               
<artifactId>spring-cloud-starter-alibaba-nacos-discovery</artifactId>
               <version>2.2.2.RELEASE</version>
           </dependency>
           <dependency>
               <groupId>org.apache.dubbo</groupId>
               <artifactId>dubbo-spring-boot-starter</artifactId>
               <version>2.7.8</version>
           </dependency>
           <dependency>
               <groupId>org.apache.dubbo</groupId>
               <artifactId>dubbo-registry-nacos</artifactId>
               <version>2.7.8</version>
           </dependency>
   ```
   
   
   
   配置文件
   
   ```yaml
   dubbo:
     registry:
       address: nacos://${spring.cloud.nacos.discovery.server-addr}
       parameters[namespace]: ${spring.cloud.nacos.discovery.namespace}
     consumer:
       # 关闭所有服务的启动时检查 (没有提供者时报错)
       check: false
     protocol:
       name: dubbo
       port: -1
   ```
   
   
   
   结果(每页10个, 已经有50个了)
   
   
![image-20211123105735738](https://user-images.githubusercontent.com/49888630/142965157-b8533cbf-0726-405f-8c4d-a15c25d07adc.png)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to