-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can not get cluster name in registry config 'service.vgroupMapping.storage_service_group', please make sure registry config correct #411
Comments
请问您解决了么 我按照这个方式还是报这个错 |
版本1.4.1,报同样的错误: 尝试各种方法,未解决 |
未解决 |
在application.properties中添加 |
@pangchun 感谢你的回答,我也是dataId没有指定service.vgroupMapping,问题是seata1.4.2已经支持以dataId = "seata-server.properties"形式读取键值,可能是client的seata版本低了 |
为什么感觉这个seata这么难用呀. |
我觉得挺好用的,不知道你是指哪方面难用 |
抱歉是我口嗨了,大致就是配置方面吧.就像这里出现的问题.我也是通过您这条回答解决的.虽然解决了,还是觉得官方文档没有说清楚吧. |
说实话seata配置这块的官方文档和demo确实不够清晰,很多资深开发都搞不明白 |
version:
seata:1.4.0
nacos:1.4.0
spring-boot:2.2.2.RELEASE
spring-cloud:Hoxton.SR1
In the high version of Seata, if you should use the
service.vgroupMapping.order-service-group=default
, an underline will cause the service not to be foundHope to be able to describe the exception clearly, without users to guess
and
service.vgroupMapping.order_service_group=default
also errorThe text was updated successfully, but these errors were encountered: