pinxiong commented on issue #8689: URL: https://github.com/apache/dubbo/issues/8689#issuecomment-917386652
Thanks for your summary! It's very important for community to solve those issues. To solve question 1 and 2 you've mentioned above, I totally agree with you that we need to update UT if want to fix them. I also raised some of these problems in the community weekly metting yesterday. I can share the conclusions with you below + We will try to add a new module named `dubbo-mock` to mork some middleware such as `nacos server` or `zookeeper server`, which need to improve their connections, time-consuming and make them shared in the whole module. Because these middlewares are widely used in some complex scenarios, which are used as` registry center` or `metadata center`. + The community will manage the lifecycle of all applied resources, such as `MetadataReport`, `ConfigManager`, `Thread` etc. after multi-instance feature in `3.0.3` releases in month(may be in next week). After all of these are over, I think all of issues you raised above will have a lot of improvement. Admittedly, the question 1 and 2 cannot be completely solved, so your summary is very important at that time. Are you interested in building `dubbo-mock` moudle with us first? -- 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: notifications-unsubscr...@dubbo.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org For additional commands, e-mail: notifications-h...@dubbo.apache.org
