Can we migrate from 2.5.0 in single step or we need to follow all below steps
For a rolling upgrade:
1. Update server.properties on all brokers and add the following properties.
CURRENT_KAFKA_VERSION refers to the version you are upgrading from.
CURRENT_MESSAGE_FORMAT_VERSION refers to the message format version currently
in use. If you have previously overridden the message format version, you
should keep its current value. Alternatively, if you are upgrading from a
version prior to 0.11.0.x, then CURRENT_MESSAGE_FORMAT_VERSION should be set to
match CURRENT_KAFKA_VERSION.
* inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g., 2.7, 2.6,
etc.)
* log.message.format.version=CURRENT_MESSAGE_FORMAT_VERSION (See
potential performance impact following the
upgrade<https://kafka.apache.org/28/documentation/#upgrade_10_performance_impact>
for the details on what this configuration does.)
If you are upgrading from version 0.11.0.x or above, and you have not
overridden the message format, then you only need to override the inter-broker
protocol version.
* inter.broker.protocol.version=CURRENT_KAFKA_VERSION (e.g., 2.7, 2.6,
etc.)
1. Upgrade the brokers one at a time: shut down the broker, update the code,
and restart it. Once you have done so, the brokers will be running the latest
version and you can verify that the cluster's behavior and performance meets
expectations. It is still possible to downgrade at this point if there are any
problems.
2. Once the cluster's behavior and performance has been verified, bump the
protocol version by editing inter.broker.protocol.version and setting it to 2.8.
3. Restart the brokers one by one for the new protocol version to take
effect. Once the brokers begin using the latest protocol version, it will no
longer be possible to downgrade the cluster to an older version.
4. If you have overridden the message format version as instructed above,
then you need to do one more rolling restart to upgrade it to its latest
version. Once all (or most) consumers have been upgraded to 0.11.0 or later,
change log.message.format.version to 2.8 on each broker and restart them one by
one. Note that the older Scala clients, which are no longer maintained, do not
support the message format introduced in 0.11, so to avoid conversion costs (or
to take advantage of exactly once
semantics<https://kafka.apache.org/28/documentation/#upgrade_11_exactly_once_semantics>),
the newer Java clients must be used.
On 2022/04/11 06:07:15 Luke Chen wrote:
> Hi Vinay,
>
> This doc should help:
> https://kafka.apache.org/28/documentation/#upgrade
>
> Thank you.
> Luke
>
> On Mon, Apr 11, 2022 at 12:43 PM vinay kumar
> <vi...@gmail.com<mailto:vi...@gmail.com>>
> wrote:
>
> > Hi,,
> >
> > Is there any wiki to migrate from 2.5.0 to 2.8.0 In production
> >
> > Thanks,
> > Vinay
> >
>
