You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dubbo.apache.org by GitBox <gi...@apache.org> on 2018/04/18 05:42:15 UTC

[GitHub] YoungHu opened a new issue #1624: [Design bug] unreasonable design for register dubbo service

YoungHu opened a new issue #1624: [Design bug] unreasonable design for register dubbo service
URL: https://github.com/apache/incubator-dubbo/issues/1624
 
 
   when using dubbo in production env, we found that in specific scenes(register same interface with multiplay group or version)  service register will cause zookeeper output huge data for a long time. the reason is when service export, it will notice all consumers who described the interface but **NOT interface&group or version**. the root reason is dubbo store all of the services or consumers under interfacde node and not split them with group or version. now we forked dubbo source code then did the split operation, want to know if official have any good idea.  
   
   BTW, I did a test and record it in my [CSDN Blog](https://blog.csdn.net/huyong1990/article/details/79988177)

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