THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Status
Current state: Draft
Discussion thread: here [Change the link from the KIP proposal email archive to your own email thread]
JIRA: here [Change the link from KAFKA-1 to your own ticket]
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
The Apache Kafka project has retained support for all protocol API versions since Apache Kafka 0.8.0 (released 9+ years ago on December 2013). As time goes on, the cost of maintaining support for all these versions goes up (both in code complexity and the testing matrix) and the value goes down (as users switch to clients that rely on newer protocol API versions). Apache Kafka 4.0 presents a good opportunity to re-evaluate this policy since it includes other modernization initiatives like dropping support for zk mode and dropping support for message formats v0 and v1 (KIP-724). No date has been set for Apache Kafka 4.0, but it's safe to say it won't happen before the end of 2023.
We propose setting the new baseline for protocol API versions to Apache Kafka 2.1 (released 4+ years ago on Nov 2018). More concretely, for each protocol API, we will only keep the most recent version supported by Apache Kafka 2.1 as well as any version introduced after Apache Kafka 2.1. We deviate from the proposed baseline in a number of cases based on existing clients support. In order to determine client support for the various protocol API versions, we take the latest client release at the end of 2021 - this gives it a better chance of being widely used.
We believe there is merit in having a general protocol API versioning policy that can be applied mechanically on each new major version - we intend to submit a separate KIP for that. It would only apply from Apache Kafka 5.0 to give the ecosystem plenty of time to adapt.
Public Interfaces
Remove support for the following protocol API versions (the range is inclusive):
- Produce: V0-V6
- Fetch: V0-V9
- ListOffset: V0-V1 due to clients (librdkafka, KafkaJS, Sarama) support – V0-V3 per the baseline
- Metadata: V0-V3 due to clients (librdkafka, KafkaJS, Sarama, kafka-python) support – V0-V6 per the baseline
- OffsetCommit: V0-V2 due to clients (KafkaJS, Sarama, kafka-python) support – V0-V5 per the baseline
- OffsetFetch: V0-V2 due to clients (KafkaJS, kafka-python) support – V0-V4 per the baseline
- FindCoordinator: V0 due to clients (Sarama, kafka-python) support – V0-V1 per the baseline
- JoinGroup: V0-V1 due to clients (Sarama, kafka-python) support – V0-V2 per the baseline
- Heartbeat: none due to clients (Sarama, kafka-python) support – V0-V1 per the baseline
- LeaveGroup: none due to clients (librdkafka, Sarama, kafka-python) support – V0-V1 per the baseline
- SyncGroup: none due to clients (Sarama) support – V0-V1 per the baseline
- DescribeGroups: none due to clients (librdkafka, Sarama) support – V0-V1 per the baseline
- ListGroups: none due to clients (librdkafka, Sarama) support – V0-V1 per the baseline
- SaslHandshake: V0
- ApiVersions: V0-V1
- CreateTopics: V0-V1 due to clients (Sarama) support – V0-V2 per the baseline
- DeleteTopics: V0 due to clients (librdkafka, KafkaJS, Sarama) support – V0-V2 per the baseline
- DeleteRecords: none due to clients (Sarama) support – V0 per the baseline
- InitProducerId: none due to clients (Sarama) support – V0 per the baseline
- OffsetForLeaderEpoch: V0-V1
- librdkafka: none
- KafkaJS: none
- Sarama: none
- kafka-python: none
- AddPartitionsToTxn: none due to clients (librdkafka, Sarama) support – V0 per the baseline
- AddOffsetsToTxn: none due to clients (librdkafka, Sarama) support – V0 per the baseline
- EndTxn: none due to clients (Sarama) support – V0 per the baseline
- WriteTxnMarkers: none
- TxnOffsetCommit: none due to clients (KafkaJS, Sarama) support – V0-V1 per the baseline
- DescribeAcls: V0
- CreateAcls: V0
- DeleteAcls: V0
- DescribeConfigs: V0 due to clients (librdkafka) support – V0-V1 per the baseline
- AlterConfigs: none due to clients (librdkafka, Sarama) support – V0 per the baseline
- AlterReplicaLogDirs: V0
- librdkafka: none
- KafkaJS: none
- Sarama: none
- kafka-python: none
- DescribeLogDirs: V0
- librdkafka: none
- KafkaJS: none
- Sarama: V1
- kafka-python: none
- SaslAuthenticate: None
- CreatePartitions: none due to clients (librdkafka, Sarama) support – V0 per the baseline
- CreateDelegationToken: V0
- librdkafka: none
- KafkaJS: none
- Sarama: none
- kafka-python: none
- RenewDelegationToken: V0
- librdkafka: none
- KafkaJS: none
- Sarama: none
- kafka-python: none
- ExpireDelegationToken: V0
- librdkafka: none
- KafkaJS: none
- Sarama: none
- kafka-python: none
- DescribeDelegationToken: V0
- librdkafka: none
- KafkaJS: none
- Sarama: none
- kafka-python: none
- DeleteGroups: V0
Additional information regarding the client releases used for the analysis above:
- librdkafka 1.8.2, released on October 2021 (note that a number of clients are built on top of librdkafka - a few examples are Confluent's clients for Python, .NET & Go, node-rdkafka and rdkafka-ruby).
- KafkaJS 1.15.0, released on November 2020
- Sarama 1.30.1. released on December 2021
- kafka-python 2.0.2, released on Sep 2020
The Java client is part of the Apache Kafka repository, it is released alongside the broker and it generally supports the latest protocol versions exposed by the broker. Given that, we know that the Java client has supported the protocol API versions baseline set by Apache Kafka 2.1 as part of that release in November 2018 and no further analysis is required.
Proposed Changes
TBD
Compatibility, Deprecation, and Migration Plan
TBD (talk about broker metrics users can rely on to know if they're impacted and what happens if an unsupported protocol version is used)
Test Plan
- Client compatibility system tests will updated so that 2.0.x clients fail with an UNSUPPORTED_VERSION error and older versions are removed.
- Protocol API integration tests will be updated so that the highest unsupported version and lowest supported version are tested and older versions are not.
- Protocol API unit tests will continue to cover all versions, but the expectations will be updated for unsupported versions.
Rejected Alternatives
- Continue with the "support forever" compatibility policy: the benefit cost ratio is low given low usage of the older protocol API versions.