YoWuwuuuw opened a new issue, #7527: URL: https://github.com/apache/incubator-seata/issues/7527
### Check Ahead - [x] I have searched the [issues](https://github.com/seata/seata/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 When **seata-server** configures multiple registry types, if **namingserver** is included, the `namespace` will not be reported. This will cause watch api `api/v1/naming/clusters` to return data errors and other problems. ### Ⅱ. Describe what happened ### seata-server configuration: ``` registry: type: seata,nacos / seata nacos: application: seata-server server-addr: 127.0.0.1:8848 group: SEATA_GROUP namespace: default cluster: default seata: server-addr: 127.0.0.1:8081 cluster: default namespace: public heartbeat-period: 5000 metadata-max-age-ms: 30000 username: seata password: 7620ce1c # Automatically generate passwords tokenValidityInMilliseconds: 1740000 ``` ### Normal situation: `registry.type: seata` Accessing `http://localhost:8081/api/v1/naming/clusters?namespace=public` can return data normally <img width="1719" height="245" alt="Image" src="https://github.com/user-attachments/assets/31535883-16a8-4265-9d73-dce5fcc9758a"; /> ### Bug situation: `registry.type: seata,nacos` > The same configuration Accessing `http://localhost:8081/api/v1/naming/clusters?namespace=public` returns empty, which means that the `namespace` parameter has not been uploaded to **namingserver** <img width="1698" height="130" alt="Image" src="https://github.com/user-attachments/assets/3c577841-ec7c-4bdb-970b-a4203cdebd86"; /> **namingserver end log:** ` 20:05:57.183 WARN --- [ http-nio-8081-exec-1] [ngserver.manager.NamingManager] [ monitorCluster] [] : no cluster in namespace:public ` ### Ⅲ. Describe what you expected to happen Configuring **multiple registry type** has the same effect as configuring **single registry type**, for example, the watch api returns the same data. ### Ⅳ. How to reproduce it (as minimally and precisely as possible) 1. Start the **namingserver** directly through IntelliJ IDEA, get the password and configure it to `server/src/main/resources/application.yml registry.seata.password` 2. Start the **seata-server** directly through IntelliJ IDEA. 3. Use tools such as curl to access api/v1/naming/clusters The above steps are performed under registry.type: seata and registry.type: seata,nacos configuration respectively. ### Ⅴ. Anything else we need to know? _No response_ ### Ⅵ. Environment java -version: 17 -- 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...@seata.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@seata.apache.org For additional commands, e-mail: notifications-h...@seata.apache.org
