Re: [External Email] Re: Upgrading Kafka Kraft in Kubernetes

:port] upgrade > --metadata 3.6 > > This is doable using declarative Kubernetes job. > > Thank you very much, I appreciate your help. > > Jiri > > From: Jakub Scholz > Sent: Thursday, October 19, 2023 5:18 PM > To: users@kafka.apache.org > Subject: [External Email

RE: [External Email] Re: Upgrading Kafka Kraft in Kubernetes

eatures.sh --bootstrap-server [server:port] upgrade --metadata 3.6 This is doable using declarative Kubernetes job. Thank you very much, I appreciate your help. Jiri From: Jakub Scholz Sent: Thursday, October 19, 2023 5:18 PM To: users@kafka.apache.org Subject: [External Email] Re: Upgrading Kafk

Re: Upgrading Kafka Kraft in Kubernetes

Hi Jiří, Why can't you run it from another Pod? You should be able to specify --bootstrap-server and point it to the brokers to connect to. You can also pass further properties to it using the --command-config option. It should be also possible to use it from the Admin API

Re: Upgrading Kafka from Version 0.10.2 to 1.0.0

On Tue, Jan 9, 2018 at 4:50 PM, ZigSphere Tech wrote: > Is it easy to upgrade from Kafka version 0.10.2 to 1.0.0 or do I need to > upgrade to version 0.11.0 first? Anything to expect? > We just did (almost) exactly this upgrade. 2.11-0.10.1.0 to 2.11-1.0.0. The main issue we faced was the broke

Re: Upgrading Kafka to 11.0

Thanks Mani. On Tue, Sep 12, 2017 at 12:27 PM, Manikumar wrote: > Hi, > > Yes, you can replace bin and libs folders. or you can untar to a new folder > and > update config/server.properties config file. > > On Tue, Sep 12, 2017 at 12:21 PM, kiran kumar > wrote: > > > [re-posting] > > > > Hi All

Re: Upgrading Kafka to 11.0

Hi, Yes, you can replace bin and libs folders. or you can untar to a new folder and update config/server.properties config file. On Tue, Sep 12, 2017 at 12:21 PM, kiran kumar wrote: > [re-posting] > > Hi All, > >1. Upgrade the brokers one at a time: shut down the broker, update the >cod

Re: Upgrading Kafka to 11.0

[re-posting] Hi All, 1. Upgrade the brokers one at a time: shut down the broker, update the code, and restart it. What does it mean to "update the code". Does it mean replace the old lib folder with latest ? or replace lib and bin with latest? Could someone clarify ? On Fri, Sep 8, 2017

Re: upgrading Kafka

Yes,you can use constraints and same volumes.That can be trusted. From: Radoslaw Gruchalski To: "Karnam, Kiran" ; users@kafka.apache.org Sent: Thursday, 26 May 2016 2:31 AM Subject: Re: upgrading Kafka Kiran, If you’re using Docker, you can use Docker on Mesos, y

Re: upgrading Kafka

More specifically, see: https://github.com/mesos/kafka#failed-broker-recovery On Wed, May 25, 2016 at 6:02 PM, craig w wrote: > The Kafka framework can be used to deploy brokers. It will also bring a > broker back up on the server it was last running on (within a certain > amount of time). > > H

Re: upgrading Kafka

The Kafka framework can be used to deploy brokers. It will also bring a broker back up on the server it was last running on (within a certain amount of time). However the Kafka framework doesn't run brokers in containers. On Wednesday, May 25, 2016, Radoslaw Gruchalski wrote: > Kiran, > > If yo

Re: upgrading Kafka

Kiran, If you’re using Docker, you can use Docker on Mesos, you can use constraints to force relaunched kafka broker to always relaunch at the same agent and you can use Docker volumes to persist the data. Not sure if https://github.com/mesos/kafka provides these capabilites. – Best regards,