[jira] [Commented] (BEAM-11656) Savepoints stuck in IN_PROGRESS state in beam 2.27

["Beam JIRA Bot (Jira)" <ji...@apache.org>]

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

Beam JIRA Bot commented on BEAM-11656:
--------------------------------------

This issue is P2 but has been unassigned without any comment for 60 days so it has been labeled "stale-P2". If this issue is still affecting you, we care! Please comment and remove the label. Otherwise, in 14 days the issue will be moved to P3.

Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed explanation of what these priorities mean.


> 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, stale-P2
>         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)