[GitHub] [flink-table-store] tsreaper opened a new pull request, #225: [FLINK-28605] Throw exception intentionally when new snapshots are committed during restore

[GitBox <gi...@apache.org>]

tsreaper opened a new pull request, #225:
URL: https://github.com/apache/flink-table-store/pull/225

   Currently snapshots are committed in `notifyCheckpointComplete`. If the job fails between a successful checkpoint and the call of `notifyCheckpointComplete`, these snapshots will be committed after job restarts.
   
   However when the writer starts they also need to read from the latest snapshot (to build the latest structure of LSM tree). These two steps may happen concurrently and what the writers see may not be the latest snapshot.
   
   To fix this problem, we can throw exception intentionally after new snapshots are committed during restore. In this way the job will be forcefully restarted and it is very likely that the writers can see the latest snapshot.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [flink-table-store] JingsongLi merged pull request #225: [FLINK-28605] Throw exception intentionally when new snapshots are committed during restore

[GitBox <gi...@apache.org>]

JingsongLi merged PR #225:
URL: https://github.com/apache/flink-table-store/pull/225


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org