bachmanity1 opened a new pull request, #16968: URL: https://github.com/apache/kafka/pull/16968
Currently, when the `DescribeCluster` API with `EntityType=1` or the `TopicMetadata` API is called, the controller ID value in the response is set to a random broker ID. I'm not sure but I think this approach was used because, before KIP-919, clients couldn't communicate directly with the controller and had to route through a broker. Therefore, the specific broker used to reach the controller didn't matter. However, after KIP-919, it would be more appropriate to return the actual controller ID if the node also serves as a broker. Otherwise, return -1 to avoid confusing users. **Summary:** **AS-IS:** - `DescribeCluster` with `EntityType=1` or `TopicMetadata` request -> controller ID is set to a random broker ID. **TO-BE:** - `DescribeCluster` with `EntityType=1` or `TopicMetadata` request -> controller ID is set to the actual controller ID if it also serves as a broker; otherwise, return -1. ### Committer Checklist (excluded from commit message) - [ ] Verify design and implementation - [ ] Verify test coverage and CI build status - [ ] Verify documentation (including upgrade notes) -- 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: jira-unsubscr...@kafka.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
