[ 
https://issues.apache.org/jira/browse/FLINK-22267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321920#comment-17321920
 ] 

Jark Wu commented on FLINK-22267:
---------------------------------

>From the log information, it did restore source offset state from the 
>savepoint, however, the restored source offset is not existed in the kafka 
>topic (cleaned by your step 2). In this case, Kafka will reset offset to 
>earliest by default, see Kafka property {{auto.offset.reset}}.

> Savepoint an application for source of upsert-kafka, then restart the 
> application from the savepoint, state not be recovered.  
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-22267
>                 URL: https://issues.apache.org/jira/browse/FLINK-22267
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.12.2
>            Reporter: Carl
>            Priority: Major
>         Attachments: image-2021-04-14-11-17-00-207.png
>
>
> My operation is as follows:
> 1. Savepoint an application for source of upsert-kafka
> 2. Delete the upsert Kafka topic data
> 3. restart the application from the savepoint
> 4. Log shows that the offset has been restored, but the state has not been 
> restored
> What I want to confirm is that restart from savepoint in the source 
> upsert-kafka application not restore the state from savepoint state but 
> restore the state from earliest offset kafka message?
> If so, why reset offset:
> !image-2021-04-14-11-17-00-207.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to