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

José Armando García Sancio updated KAFKA-16538:
-----------------------------------------------
    Description: 
Should:
 # Route request to cluster metadata kraft client.
 # KRaft leader should check the supported version of all voters and observers
 ## voter information comes from VoterSet
 ## observer information is push down to kraft by the metadata controller
 # Persist both the kraft.version and voter set in one control batch

We need to allow for the kraft.version to succeed while the metadata controller 
changes may fail. This is needed because there will be two batches for this 
updates. One control record batch which includes kraft.version and voter set, 
and one metadata batch which includes the feature records.

 

This change should also improve the handling of UpdateVoter to allow the 
request when the kraft.version is 0.

  was:
Should:
 # Route request to cluster metadata kraft client.
 # KRaft leader should check the supported version of all voters and observers
 ## voter information comes from VoterSet
 ## observer information is push down to kraft by the metadata controller
 # Persist both the kraft.version and voter set in one control batch

We need to allow for the kraft.version to succeed while the metadata controller 
changes may fail. This is needed because there will be two batches for this 
updates. One control record batch which includes kraft.version and voter set, 
and one metadata batch which includes the feature records.


> UpdateFeatures for kraft.version
> --------------------------------
>
>                 Key: KAFKA-16538
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16538
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: José Armando García Sancio
>            Priority: Major
>
> Should:
>  # Route request to cluster metadata kraft client.
>  # KRaft leader should check the supported version of all voters and observers
>  ## voter information comes from VoterSet
>  ## observer information is push down to kraft by the metadata controller
>  # Persist both the kraft.version and voter set in one control batch
> We need to allow for the kraft.version to succeed while the metadata 
> controller changes may fail. This is needed because there will be two batches 
> for this updates. One control record batch which includes kraft.version and 
> voter set, and one metadata batch which includes the feature records.
>  
> This change should also improve the handling of UpdateVoter to allow the 
> request when the kraft.version is 0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to