Re: [PR] fix(polaris): reconcile initial subscribe snapshot [dubbo-go]

Tue, 14 Jul 2026 04:05:31 -0700 


Alanxtl commented on PR #3482:
URL: https://github.com/apache/dubbo-go/pull/3482#issuecomment-4968462690

   > > lgtm 你实际运行 
https://github.com/apache/dubbo-go-samples/tree/main/registry/polaris 试一下 
之前的场景还会出现问题吗
   > 
   > 测试时先临时拉长了 LoadSubscribeInstances 与 Subscribe 之间的窗口（90秒）。client 初始同步 Load 到 
provider A（127.0.0.1:20000），在 Subscribe 建立前启动 provider B（127.0.0.1:20001），然后再停止 
A，首次 WatchService 完整快照中只包含 B。之前的场景不会再出现问题了
   > 
   > 日志中标出了：
   > 
   > * 初始 selector add A
   > * 90秒窗口
   > * 首次快照触发 DELETE(A)，并从 selector 中删除 A
   > * 随后触发 ADD(B)，并将 B 加入 selector
   > * 最后调用 B
   > 
   > <img alt="9fe2657f8013f0cf547a419fefadda28" width="2000" height="1122" 
src="https://private-user-images.githubusercontent.com/237921636/621406994-aaeafad9-10ac-4975-aa6b-bc1142e43b4a.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODQwMjc0MDYsIm5iZiI6MTc4NDAyNzEwNiwicGF0aCI6Ii8yMzc5MjE2MzYvNjIxNDA2OTk0LWFhZWFmYWQ5LTEwYWMtNDk3NS1hYTZiLWJjMTE0MmU0M2I0YS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNzE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDcxNFQxMTA1MDZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZmMwNGYxZDYzMDhkNjEwMGU3MDA4MTRmMDViNTc4NTE3ZDNjNzk2MDA4NjczMmI5MjkzOTc5MTVlZDEwM2I5JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.zu7QHofC3PByey6nPrEjvKwo1b-od3ZA9fJ2S_yfdaM";>
   
   cool


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