I am not 100% sure what you exactly do to upgrade to 2.1. But if you add a `suppress()` operator, you change your topology and therefore the old and new program is not compatible any longer.
To avoid breaking changes like this, you can now (since 2.1) name all operators, stores, and changelog topic. This will allow future upgrade without resetting the application. Hope this helps. -Matthias On 12/27/18 10:09 AM, 徐华 wrote: > Hi, > > I am use kafka stream new feature in kafka. > My kafka vision : 2.0 > My kafka-client vision : 2.1 > But i can use the new feature : KIP-328-Final window results per key > <https://cwiki.apache.org/confluence/display/KAFKA/KIP-328%3A+Ability+to+suppress+updates+for+KTables#KIP-328:AbilitytosuppressupdatesforKTables-Finalwindowresultsperkey> > When i update my application every time, the kafka stream will shutdown. > So i have to delete all topic and restart ,then it work . > Error detail as below: > > 2018-12-27 03:44:23.071|INFO > |flash-client-bch-StreamThread-2|o.a.k.s.p.i.StoreChangelogReader|215|stream-thread > [flash-client-bch-StreamThread-2] No checkpoint found for task 12_1 state > store user-share-store-minute changelog > flash-app-bch-user-share-store-minute-changelog-1 with EOS turned on. > Reinitializing the task and restore its state from the beginning. > 2018-12-27 03:44:23.080|INFO > |flash-client-bch-StreamThread-2|o.a.k.s.p.i.StoreChangelogReader|215|stream-thread > [flash-client-bch-StreamThread-2] No checkpoint found for task 1_1 state > store user-speed-hs5m-store-avg changelog > flash-app-bch-user-speed-hs5m-store-avg-changelog-1 with EOS turned on. > Reinitializing the task and restore its state from the beginning. > 2018-12-27 03:44:23.087|INFO > |flash-client-bch-StreamThread-2|o.a.k.c.c.KafkaConsumer|1031|[Consumer > clientId=flash-client-bch-StreamThread-2-restore-consumer, groupId=] > Unsubscribed all topics or patterns and assigned partitions > 2018-12-27 03:44:26.670|INFO > |http-nio-8080-exec-1|o.a.c.c.C.[.[.[/]|173|Initializing Spring > DispatcherServlet 'dispatcherServlet' > 2018-12-27 03:44:26.671|INFO > |http-nio-8080-exec-1|o.s.w.s.DispatcherServlet|521|Initializing Servlet > 'dispatcherServlet' > 2018-12-27 03:44:26.699|INFO > |http-nio-8080-exec-1|o.s.w.s.DispatcherServlet|543|Completed > initialization in 27 ms > 2018-12-27 03:46:05.305|INFO > |org.springframework.kafka.KafkaListenerEndpointContainer#1-0-C-1|o.a.k.c.FetchSessionHandler|381|[Consumer > clientId=consumer-16, groupId=user-share-group] Node 1 was unable to > process the fetch request with (sessionId=1872699174, epoch=119): > INVALID_FETCH_SESSION_EPOCH. > 2018-12-27 03:46:05.306|INFO > |org.springframework.kafka.KafkaListenerEndpointContainer#1-0-C-1|o.a.k.c.FetchSessionHandler|381|[Consumer > clientId=consumer-16, groupId=user-share-group] Node 2 was unable to > process the fetch request with (sessionId=2143576707, epoch=119): > INVALID_FETCH_SESSION_EPOCH. > 2018-12-27 03:46:05.306|INFO > |org.springframework.kafka.KafkaListenerEndpointContainer#1-0-C-1|o.a.k.c.FetchSessionHandler|381|[Consumer > clientId=consumer-16, groupId=user-share-group] Node 0 was unable to > process the fetch request with (sessionId=2073820316, epoch=119): > INVALID_FETCH_SESSION_EPOCH. > > Thanks > Xu >
signature.asc
Description: OpenPGP digital signature
