seata2.5.0使用nameserver为注册中心以后客户端集成失败,启动报错
Check Ahead
-
[x] I have searched the issues of this repository and believe that this is not a duplicate.
-
[x] I am willing to try to fix this bug myself.
Ⅰ. Issue Description
seata2.5.0使用nameserver为注册中心以后客户端集成失败,启动报错,报错信息为:no available service found in cluster. After using nameserver as the registration center in seata2.5.0, client integration fails and an error message is reported on startup: no available service found in cluster.
client-config:
server-config:
浏览器访问控制台正常/The browser can access the console normally. 使用seata为注册中心有详细的使用文档吗/Is there a detailed usage document for using Seata as a registration center?
Ⅱ. Describe what happened
No response
Ⅲ. Describe what you expected to happen
No response
Ⅳ. How to reproduce it (as minimally and precisely as possible)
No response
Ⅴ. Anything else we need to know?
No response
Ⅵ. Environment
springboot3.5.6 jdk21 单机版的seata和nameserver
starter版本为2.5.0 报错的信息如下:
You can try starting TC first, and then start the client
thats great mate
You can try starting
TCfirst, and then start theclient
TC一直都是好的,控制台访问正常
Have you registered the transaction group with the naming server using its API?
https://seata.apache.org/zh-cn/docs/next/user/registry/namingserver#%E5%88%9B%E5%BB%BAclient%E7%AB%AF%E7%9A%84%E4%BA%8B%E5%8A%A1%E5%88%86%E7%BB%84-seata%E9%9B%86%E7%BE%A4%E7%9A%84%E6%98%A0%E5%B0%84%E5%85%B3%E7%B3%BB
Have you registered the transaction group with the naming server using its API?
注册以后还是有问题,使用默认的分组订阅关系也不行,换成nacos就没这个问题,这一块能否提供一个详细的文档呢,特别是客户端集成的时候,这一款我看了基本没什么参考资料的 There are still problems after registration. Using the default group subscription relationship doesn’t work either. Switching to Nacos doesn’t have this issue. Could you provide a detailed document on this, especially for client integration? I’ve seen that there’s basically no reference material for this one.
What cluster have you configured for your Seata Server? How do you register the relationship between your transaction groups and that cluster? And how is the server side configured?
Also, has the vgroup_table been created in the server's corresponding database?