[
https://issues.apache.org/jira/browse/KAFKA-7481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659935#comment-16659935
]
Ewen Cheslack-Postava commented on KAFKA-7481:
----------------------------------------------
[~ijuma] As it stands today, is the only use case for
inter.broker.protocol.version to hold back the version during rolling upgrade?
Do we even really need this with KIP-35? It sounds like aside from the two
rolling bounce upgrade, you expect people wouldn't generally be using this
today (given you say the benefit is minimal)?
I'm fine overloading one of them if we think the existing use case for it is
either ok to compromise with additional restrictions OR tradeoffs aren't weird
like they are for log.message.format.version. Test surface area is a fair
point, wrt complexity I guess I don't see that much of a difference for users
since they just copy/paste 2 lines rather than 1 and otherwise probably blindly
follow the directions.
> Consider options for safer upgrade of offset commit value schema
> ----------------------------------------------------------------
>
> Key: KAFKA-7481
> URL: https://issues.apache.org/jira/browse/KAFKA-7481
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Priority: Blocker
> Fix For: 2.1.0
>
>
> KIP-211 and KIP-320 add new versions of the offset commit value schema. The
> use of the new schema version is controlled by the
> `inter.broker.protocol.version` configuration. Once the new inter-broker
> version is in use, it is not possible to downgrade since the older brokers
> will not be able to parse the new schema.
> The options at the moment are the following:
> 1. Do nothing. Users can try the new version and keep
> `inter.broker.protocol.version` locked to the old release. Downgrade will
> still be possible, but users will not be able to test new capabilities which
> depend on inter-broker protocol changes.
> 2. Instead of using `inter.broker.protocol.version`, we could use
> `message.format.version`. This would basically extend the use of this config
> to apply to all persistent formats. The advantage is that it allows users to
> upgrade the broker and begin using the new inter-broker protocol while still
> allowing downgrade. But features which depend on the persistent format could
> not be tested.
> Any other options?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
