You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Ashish K Singh (JIRA)" <ji...@apache.org> on 2016/05/19 23:56:13 UTC

[jira] [Updated] (KAFKA-3308) Use ProtocolVersion during rolling upgrades to decide on a mutually agreed protocol version between brokers, eliminating the need of inter.broker.protocol.version.

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

Ashish K Singh updated KAFKA-3308:
----------------------------------
    Description: 
inter.broker.protocol.version configuration was nice for few releases, but it is getting to be a pain to maintain, remember to update, it breaks on trunk upgrades, etc.
Since we have KIP-35, the controller can actually check for specific versions supported by brokers for specific API requests. Why not use that and get rid of the configuration?
We already maintain the protocol versions anyway, upgrades will be smoother, and we'll support upgrades between any two patches.

> Use ProtocolVersion during rolling upgrades to decide on a mutually agreed protocol version between brokers, eliminating the need of inter.broker.protocol.version.
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-3308
>                 URL: https://issues.apache.org/jira/browse/KAFKA-3308
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Ashish K Singh
>            Assignee: Ashish K Singh
>
> inter.broker.protocol.version configuration was nice for few releases, but it is getting to be a pain to maintain, remember to update, it breaks on trunk upgrades, etc.
> Since we have KIP-35, the controller can actually check for specific versions supported by brokers for specific API requests. Why not use that and get rid of the configuration?
> We already maintain the protocol versions anyway, upgrades will be smoother, and we'll support upgrades between any two patches.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)