[KAFKA-16538] Support UpdateFeatures for kraft.version so we can go from static quorums to dynamic

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: José Armando García Sancio
• Reporter: José Armando García Sancio
• Created: 11/Apr/24 20:53
• Updated: Yesterday 17:11

Description

Should:

1. Route request to cluster metadata kraft client.
2. KRaft leader should check the supported version of all voters and observers
   1. voter information comes from VoterSet
   2. observer information is push down to kraft by the metadata controller
3. 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.

Issue Links

• is duplicated by: KAFKA-17866 kraft.version/dirID is not updated after upgrading to MV 3.9