Hello Soman,
again, hard to tell, this is what the docs say:
"...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.
"
also:
"...Once the brokers begin using the latest protocol version, it will no
longer be po
Hello Jonathan,
I believe I did not set *log.message.format.version* to the current version
before I upgraded to 2.3. However, I did set inter.broker.protocol.version
though. Would reverting back to 0.10.1 and upgrading again with
*log.message.format.version
*work?
Thanks,
Soman
On Sun, Dec 8, 20
Hard to tell without logs and more context, I mean, Is a big jump from
0.10.1 to 2.3.1.
Did you follow all the instructions/comments? as in the upgrade
documentation https://kafka.apache.org/documentation/#upgrade_2_3_0?
Cheers!
--
Jonathan
On Sun, Dec 8, 2019 at 3:18 PM Soman Ullah wrote:
>
Hello Jonathan,
I've installed the same version on all the brokers. The brokers were
restarted as well. Any suggestions on how I can fix this?
Thanks,
Soman
On Sat, Dec 7, 2019 at 9:17 AM Jonathan Santilli
wrote:
> Hello,
>
> have you ensured you have installed the same version in all brokers?
Hello,
have you ensured you have installed the same version in all brokers? Did
you restart all brokers after the update as indicated in the rolling
upgrade instructions?
Cheers!
On Sat, Dec 7, 2019, 2:38 PM Soman Ullah wrote:
> Hello,
>
> I recently upgraded our kafka cluster from Kafka versi
Hello,
I recently upgraded our kafka cluster from Kafka version 0.10.1 to 2.3.1
I've confirmed the version has updated using the following command:
/home/wrte/install/kafka/bin/kafka-topics.sh --version
2.3.1.1_212.11 (Commit:8c923fb4c62a38ae)
However I'm unable to use the transactional features
