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

Yuan Mei edited comment on FLINK-25261 at 12/22/21, 9:06 AM:
-------------------------------------------------------------

1. What does "truncation" mean? It means from seq # x, data is safe to delete.
2. Materialization up to seq # y means *new* checkpoints will not depend on log 
changes before seq # y. But it does not necessarily mean all data before y can 
be deleted (*old* checkpoints may also depend on some parts before y).
3. what exactly are the `in-memory` data here? Those are not flushed to DFS? 
Then what about those already flushed to DFS, but not within any checkpoint yet 
(not within any state)?



was (Author: ym):
1. What does "truncation" mean? It means from seq # x, data is safe to delete.
2. Materialization up to seq # y means new checkpoints will not depend on log 
changes before seq # y. But it does not necessarily mean all data before y can 
be deleted (old checkpoints may also depend on some parts before y).
3. what exactly are the `in-memory` data here? Those are not flushed to DFS? 
Then what about those already flushed to DFS, but not within any checkpoint yet 
(not within any state)?


> Changelog not truncated on materialization
> ------------------------------------------
>
>                 Key: FLINK-25261
>                 URL: https://issues.apache.org/jira/browse/FLINK-25261
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / State Backends
>    Affects Versions: 1.15.0
>            Reporter: Roman Khachatryan
>            Assignee: Roman Khachatryan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> [https://github.com/apache/flink/blob/dcc4d43e413b20f70036e73c61d52e2e1c5afee7/flink-state-backends/flink-statebackend-changelog/src/main/java/org/apache/flink/state/changelog/ChangelogKeyedStateBackend.java#L640]



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to