GitHub user funky-eyes closed the discussion with a comment: seata2.5的namingserver启动后，控制台查询报404
> registry: type: nacos,seata Caused by: > org.apache.seata.common.exception.NotSupportYetException: not support > registry type: nacos,seata at > org.apache.seata.discovery.registry.RegistryType.getType(RegistryType.java:83) > ~[seata-all-2.5.0.jar:2.5.0] at > org.apache.seata.discovery.registry.RegistryFactory.buildRegistryService(RegistryFactory.java:57) > ~[seata-all-2.5.0.jar:2.5.0] at > org.apache.seata.discovery.registry.RegistryFactory.access$100(RegistryFactory.java:31) > ~[seata-all-2.5.0.jar:2.5.0] at > org.apache.seata.discovery.registry.RegistryFactory$RegistryFactoryHolder.(RegistryFactory.java:65) > ~[seata-all-2.5.0.jar:2.5.0] The design where only the server side supports exposing services to multiple registry centers, while the client side supports discovering services from just a single registry center, is fully sufficient for registry migration scenarios. GitHub link: https://github.com/apache/incubator-seata/discussions/7703#discussioncomment-15345937 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
