Not the frameworks but applications running on the framework. I am talking about the rolling upgrade of a topology (not the entire cluster). Similar to blue green deployments of microservices
On Aug 26, 2016 9:35 PM, "Harsha Chintalapani" <[email protected]> wrote: > Abhishek, > Are you looking rolling upgrade kafka cluster or storm? > Harsha > > On Fri, Aug 26, 2016 at 6:18 AM Abhishek Agarwal <[email protected]> > wrote: > >> >> On Aug 26, 2016 2:50 PM, "Abhishek Agarwal" <[email protected]> wrote: >> >> > >> >> > Here is an interesting use case - To upgrade a topology without any >> downtime. Let's say, the topology has only Kafka as a source and two >> versions of it are running (different topology names of course) in parallel >> and sharing the kafka input load. >> > >> > In old kafka spout, rolling upgrade is not possible, partition >> assignment is derived from the number of tasks in the topology. >> > >> > In new kafka spout, partition assignment is done externally by Kafka >> server. If I deploy two different topologies with same* kafka consumer >> group id*, is it fair to assume that load will be automatically >> distributed across topologies? Are there any corner cases to consider? >> > >> > -- >> > Regards, >> > Abhishek Agarwal >> > >> >
