You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Wojtek Wiktorowicz (Jira)" <ji...@apache.org> on 2021/01/19 09:58:00 UTC
[jira] [Updated] (BEAM-11656) Savepoints stuck in IN_PROGRESS state
in beam 2.27
[ https://issues.apache.org/jira/browse/BEAM-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wojtek Wiktorowicz updated BEAM-11656:
--------------------------------------
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
{code:java}
KafkaIO.Read to consume messages from Kafka{code}
*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.
was:
*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
{code:java}
KafkaIO.Read to consume messages from Kafka{code}
*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-2021-01-19-10-53-29-425.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.
> Savepoints stuck in IN_PROGRESS state in beam 2.27
> --------------------------------------------------
>
> Key: BEAM-11656
> URL: https://issues.apache.org/jira/browse/BEAM-11656
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Affects Versions: 2.27.0
> Reporter: Wojtek Wiktorowicz
> Priority: P2
> Labels: kafka, savepoints
> Attachments: image (11).png
>
>
> *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
> {code:java}
> KafkaIO.Read to consume messages from Kafka{code}
> *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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)