GitHub user funky-eyes added a comment to the discussion: Whether or not bug
I believe this is a design issue rather than a clear-cut bug. The actual singletons loaded via SPI are the implementations of RegistryProvider, while the RegistryService implementations are constructed through the provide method of RegistryProvider. This architecture results in a new RegistryService instance being created each time the provide method is called. Therefore, I think we first need to determine whether RegistryService should maintain singleton behavior, rather than continuing with the current multiple-instance pattern. GitHub link: https://github.com/apache/incubator-seata/discussions/7342#discussioncomment-13218103 ---- This is an automatically sent email for dev@seata.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@seata.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@seata.apache.org For additional commands, e-mail: dev-h...@seata.apache.org
