apache / apache/beam

Savepoints stuck in IN_PROGRESS state in beam 2.27

Open
#20,713 0 comments 0 reactions 0 assignees View on GitHub
bug flink io java kafka P3 runners
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

*The problem:*
After triggering a savepoint, it's status is stuck in "IN_PROGRESS" for ever.

*Context:*
Executed with: beamn-runners-flink-1.10, beam-sdks-java-core:2.27, beam-sdks-java-io-kafka:2.27

Using 
```

KafkaIO.Read to consume messages from Kafka
```

*Observations:*
* checkpoints are no longer being executed.
* files of savepoint are being created on external fs correctly
* no exceptions visiable in jobmanager logs nor in taskmanager
* upgrading flink from 1.10.x to 1.11.3 doesn't resolve the problem

The problem exists after upgrading version of beam components to 2.27.

From flink console:

!image (11).png!

Above image presents the state of after executing savepoint. 
We can see that first operation is being fiinshed properly but ReadData/KafkaIO is still running which ( most-likely) is the cause of why savepoint stays in IN_PROGRESS state.

Imported from Jira [BEAM-11656](https://issues.apache.org/jira/browse/BEAM-11656). Original Jira may contain additional context.
Reported by: wojtekw.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.