gosonzhang opened a new issue, #5431: URL: https://github.com/apache/inlong/issues/5431
### What happened When starting DataProxy with "./dataproxy-start.sh tube", the error.log prints as follows:  I found that masterAddrInfo is set to "pulsar://xxx.xxx.xxx.xxx:6650" In the MQ cluster list information obtained from "/inlong/manager/openapi/dataproxy/getConfig", when there are multiple types of MQ, the returned results are indistinguishable: ` {"success":true,"errMsg":null,"data":{"mqClusterList":[{"url":"aaa.aaa.aaa.aaa:8000,bbb.bbb.bbb.bbb:8000","token":"abc","params":{"masterWebUrl":"http://aaa.aaa.aaa.aaa:8080"}},{"url":"pulsar://xxx.xxx.xxx.xxx:6650","token":null,"params":{"adminUrl":"http://xxx.xxx.xxx.xxx:8080","tenant":"public"}}],"topicList":[{"topic":"dataproxy_test","inlongGroupId":"dataproxy_test","m":null}]}} ` The InLong-Manager needs to return different types of MQ clusters, and The DataProxy needs to select different MQ cluster configuration parameters according to different types of sinks. ### What you expected to happen No error ### How to reproduce start DataProxy with tube token ### Environment linux ### InLong version master ### InLong Component InLong Manager, InLong DataProxy ### Are you willing to submit PR? - [X] Yes, I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
