kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ismael Juma (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (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.
Date Tue, 21 Feb 2017 16:17:44 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-3308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876227#comment-15876227
] 

Ismael Juma commented on KAFKA-3308:
------------------------------------

[~singhashish], are you planning to work on this?

> 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: Improvement
>            Reporter: Ashish Singh
>            Assignee: Ashish Singh
>              Labels: needs-kip
>
> 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.15#6346)

Mime
View raw message