[jira] [Resolved] (KAFKA-10817) Add clusterId validation to Fetch handling

["Jason Gustafson (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-10817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gustafson resolved KAFKA-10817.
-------------------------------------
    Resolution: Fixed

> Add clusterId validation to Fetch handling
> ------------------------------------------
>
>                 Key: KAFKA-10817
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10817
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Jason Gustafson
>            Assignee: David Jacot
>            Priority: Major
>
> Initially we were unsure how the clusterId would be generated by the cluster after Zookeeper removal, so we did not implement it. It is looking now like we will probably require users to generate it manually prior to starting the cluster. See here for details: https://cwiki.apache.org/confluence/display/KAFKA/KIP-631%3A+The+Quorum-based+Kafka+Controller#KIP631:TheQuorumbasedKafkaController-Fencing. In this case, we can assume that the clusterId will be provided when instantiating the raft client, so we can add the logic to the request handler to validate it in inbound Fetch requests.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)