You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2019/09/14 17:26:00 UTC

[jira] [Created] (KAFKA-8908) Use ApiVersion API for inter-broker communication

Jason Gustafson created KAFKA-8908:
--------------------------------------

             Summary: Use ApiVersion API for inter-broker communication
                 Key: KAFKA-8908
                 URL: https://issues.apache.org/jira/browse/KAFKA-8908
             Project: Kafka
          Issue Type: Improvement
            Reporter: Jason Gustafson
            Assignee: Jason Gustafson


We are probably not ready to get rid of `inter.broker.protocol.version` since we rely on it for incompatible changes to persistent schemas (e.g. consumer offsets) and in rare case for feature support (e.g. EOS). However, it is still advantageous to begin using the ApiVersion API for inter-broker communication. It allows users to test more functionality before committing to a bumped `inter.broker.protocol.version` and it reduces the impact when the value is set inconsistently between brokers. Furthermore, when there are no persistent schema changes, this opens the door to upgrades with only a single rolling restart. Longer term, now that we will have KIP-482, there is a path toward forward and backward compatible schema changes and we can rely less and less on `inter.broker.protocol.version`



--
This message was sent by Atlassian Jira
(v8.3.2#803003)