[KAFKA-10027] Implement read path for feature versioning scheme

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.0
• Assignee: Kowshik Prakasam
• Reporter: Kowshik Prakasam
• Created: 20/May/20 10:02
• Updated: 11/Jun/20 18:31
• Resolved: 11/Jun/20 18:31

Description

Goal is to implement various classes and integration for the read path of the feature versioning system (KIP-584). The ultimate plan is that the cluster-wide finalized features information is going to be stored in ZK under the node /feature. The read path implemented in this PR is centered around reading this finalized features information from ZK, and, processing it inside the Broker.

 

Here is a summary of what's needed for this Jira (a lot of it is new classes):

• A facility is provided in the broker to declare it's supported features, and advertise it's supported features via it's own BrokerIdZNode under a features key.
• A facility is provided in the broker to listen to and propagate cluster-wide finalized feature changes from ZK.
• When new finalized features are read from ZK, feature incompatibilities are detected by comparing against the broker's own supported features.
• ApiVersionsResponse is now served containing supported and finalized feature information (using the newly added tagged fields).

Issue Links

• is a parent of: KAFKA-10139 [Easy] Add operational guide for failure recovery
• links to: GitHub Pull Request #8680