Below is a plan for downtime-free upgrade of a Flink job. The downstream consumer of the Flink job is duplicate proof.
Scenario 1 - 1. Start Flink job A with consumer group G1 (12 slot job) 2. While job A is running, take a savepoint AS. 3. Start newer version of Flink job A' from savepoint AS with consumer group *G1* (12 slot job again) 4. Stop job A. Scenario 2 - 1. Start Flink job A with consumer group G1 (12 slot job) 2. While job A is running, take a savepoint AS. 3. Start newer version of Flink job A' from savepoint AS with consumer group *G2* (12 slot job again) 4. Stop job A Does it matter what consumer group job A' uses? The desired behavior is that during the window when both A and A' are running, all messages should go to both jobs. (And of course I want that job A' should start consuming from the offsets in the savepoint and not the earliest). -- View this message in context: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Does-FlinkKafkaConsumer010-care-about-consumer-group-tp14323.html Sent from the Apache Flink User Mailing List archive. mailing list archive at Nabble.com.
