liuzhiguo630 opened a new issue, #10653:
URL: https://github.com/apache/dubbo/issues/10653

   - [x] I have searched the [issues](https://github.com/apache/dubbo/issues) 
of this repository and believe that this is not a duplicate.
   
   ### Environment
   
   * Dubbo version: 3.1.0
   * Java version: 1.8.0
   
   ### Steps to reproduce this issue
   1. 在 Dubbo Provider 端配置 `dubbo.provider.delay = 1000` 并启动服务
   2. 启动过程中会发现日志 ` [DUBBO] No valid instance found, stop registering instance 
address to registry.`
   3. 启动后马上到 zookeeper 中查看 /services/xxxService/ 下,会发现并没有刚启动的这台实例的 IP
   4. 30s 后 zookeeper 上会出现实例 IP
   
   ### 问题原因
   `AbstractServiceDiscovery#register()` 在注册到注册中心时,会发现找不到元数据信息,从而报出 `No valid 
instance` 警告:
   <img width="903" alt="CleanShot 2022-09-21 at 11 57 23@2x" 
src="https://user-images.githubusercontent.com/9815635/191411072-2f4c3833-1929-4e7b-869e-c92037acf7ac.png";>
   
   而 30s 后则由 Dubbo 定时线程同步 Metadata 时发现并上报到注册中心的。
   
   怀疑是应用级注册功能,并没有实现 `dubbo.provider.delay` 延迟暴露功能,反而会有冲突,导致实际上 30s 
后才暴露。在线上这会。导致旧 Pod 已经下线,新 Pod 还没有注册上去,出现数秒到十数秒 No Provider 问题。
   


-- 
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