gosonzhang opened a new issue, #6217: URL: https://github.com/apache/inlong/issues/6217
### Description From configuration definitions and code inspection we can see: the cluster.id is not used, and indicates that the cluster and sub-cluster where DataProxy is located have been identified by proxy.cluster.name and proxy.cluster.tag. Even with cluster.id, its functionality is duplicated with these two parameters, which brings complexity to the configuration and will easily confuse users Considering that cluster.id is not used in the code logic, submit the issue for deletion: https://github.com/apache/inlong/blob/master/inlong-dataproxy/conf/common.properties#L20 ### InLong Component InLong DataProxy, InLong TubeMQ ### 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]
