Hi Gautham,
"The last 3 releases are covered and one can upgrade to the latest version
from the last previous 3" means that you should be able to do a rolling
upgrade from 3.1.x to 3.4.x.
Starting from 2.8.x one should be able to do a rolling upgrade up to 3.2.x.
It might work for newer versions b
Hi Josep,
Thanks for the speedy response. Since the last updated date on that page was
2020, I wanted to confirm I was looking at the correct page.
Also, when you say last 3 releases - do I have it right below
3.4 - current release ( and upgrade supported from 3.3,3.2,3.1?)
And what about Kafka
Hi Gautham,
You can find the general policy here:
https://cwiki.apache.org/confluence/display/KAFKA/Time+Based+Release+Plan#TimeBasedReleasePlan-WhatIsOurEOLPolicy
?
Basically, the last 3 releases are covered and one can upgrade to the
latest version from the last previous 3. Bug fixes are ported
Hi,
Can you please point me to the End of Life(EOL) policy for Kafka versions( 2.x,
3.x) as it will help us determine the need to do upgrades.
Thanks
Gautham
Hi, I have a few blogs on Kafka partitions performance for background if you
are interested:
1.
https://www.instaclustr.com/blog/the-power-of-kafka-partitions-how-to-get-the-most-out-of-your-kafka-cluster/
The Power of Apache Kafka® Partitions: How to Get the Most out of Your Kafka
Cluster<
Hi,
I'm running MM2 via Kafka Connect and i'm seeing some interesting messages
that I'm not sure about.
Basically every 5 minutes (or metadata.max.age.ms depending) i'm seeing a
message
[Producer clientId=connector-producer-mm2-source-connector-]
Resetting the last seen epoch of partition - to 0
