You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2019/01/10 16:00:00 UTC
[jira] [Resolved] (BEAM-3494) Snapshot state of aggregated data of
apache beam project is not maintained in flink's checkpointing
[ https://issues.apache.org/jira/browse/BEAM-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maximilian Michels resolved BEAM-3494.
--------------------------------------
Resolution: Incomplete
Fix Version/s: Not applicable
This is missing important information. We checkpoint in-flight data, so I don't see how something like you described is possible.
I'm closing but please feel free to re-open with more details on the issue.
> Snapshot state of aggregated data of apache beam project is not maintained in flink's checkpointing
> ----------------------------------------------------------------------------------------------------
>
> Key: BEAM-3494
> URL: https://issues.apache.org/jira/browse/BEAM-3494
> Project: Beam
> Issue Type: Bug
> Components: runner-flink
> Reporter: suganya
> Priority: Major
> Fix For: Not applicable
>
>
> We have a beam project which consumes events from kafka,does a groupby in a time window(5 mins),after window elapses it pushes the events to downstream for merge.This project is deployed using flink ,we have enabled checkpointing to recover from failed state.
> (windowsize: 5mins , checkpointingInterval: 5mins,state.backend: filesystem)
> Offsets from kafka get checkpointed every 5 mins(checkpointingInterval).Before finishing the entire DAG(groupBy and merge) , events offsets are getting checkpointed.So incase of any restart from task-manager ,new task gets started from last successful checkpoint ,but we could'nt able to get the aggregated snapshot data(data from groupBy task) from the persisted checkpoint.
> Able to retrieve the last successful checkpointed offset from kafka ,but couldnt able to get last aggregated data till checkpointing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)