Hi Kevin, I was able to take a look at the KIP today.
JS1: In the > Clusters who skip formatting will also have a static KRaft quorum, which is > explained in the below section, so controller.quorum.voters must be defined. > Operators can still end up with a dynamic quorum without formatting because > static to dynamic quorum upgrades are supported. What do you mean by "Clusters who skip formatting"? Clusters are not formatted. Users format nodes instead. Why is controller.quorum.voters required if a node skips formatting? If this is a requirement, how would the user provision a new controller (observer) node to join an existing cluster through KIP-853? The controller.quorum.voters properties should not be required in a node that will join a dynamic controller cluster. JS2: When to write version 2 of the meta.properties file? I am trying to understand when Kafka will write version 2 of the meta.properties file. I would assume that this is based on the MV but I don't see this stated explicitly in the KIP. When the MV changes to a version that supports meta.properties version 2 will Kafka automatically upgrade the version even if there are no changes to the state stored in meta.properties? JS3: How long will Kafka wait for the cluster id to be discovered? What happens if the cluster id is not in the cluster metadata partition and all of the meta.properties files? Thanks, -- -José
