Hi Manuel,
thanks. I did the three rolling restarts, or in my case three
deployments of containers with different config... But the question now
is if I should do these three restarts each time I update to latest
Kafka or if I now just change both versions to latest one without having
to do three restarts as it's just a small change and not two major versions.
I already upgraded Kafka itself from 2.1.1 to 2.3.0 in the meantime, but
still use 2.1-IV2 as Version for the log.message.format and
inter.broker.protocol... So should I do two more deployments with each
one changing one version at a time or just bump everything up to 2.3-IV1
in one go for next config-change-deployment?
Thanks
Sebastian
On 25-Jul-19 5:52 PM, Jose Manuel Vega Monroy wrote:
Hi Sebastian,
Recently we upgraded exactly from same version to that version, and
you need just two rolling restarts if you want two keep same log
format version, or three to upgrade that version too.
Personally, I would recommend you to keep those properties, for
example you could keep the current log format version for
compatibility with old clients versions.
Cheers,
Get Outlook for Android <https://aka.ms/ghei36>
From: Sebastian Schmitz
Sent: Thursday, 25 July, 03:22
Subject: [EXTERNAL] Handling of inter.broker.protocol.version and
lo.message.format.version after upgrading
To: users@kafka.apache.org
Hey guys,
I wonder what I should do with both settings for future upgrades after
having finished the upgrade from 0.10.1 to 2.1.1.
Should I just remove it from the config so it will default to the
current version of Kafka or do I have to do the rolling upgrade with
changing versions and restarting Kafka three times each time?
Thanks
Sebastian
--
DISCLAIMER
This email contains information that is confidential and which
may be
legally privileged. If you have received this email in error please
notify the sender immediately and delete the email.
This email is intended
solely for the use of the intended recipient and you may not use or
disclose this email in any way.
--
DISCLAIMER
This email contains information that is confidential and which
may be
legally privileged. If you have received this email in error please
notify the sender immediately and delete the email.
This email is intended
solely for the use of the intended recipient and you may not use or
disclose this email in any way.
