[GitHub] [beam] damccorm opened a new issue, #20713: Savepoints stuck in IN_PROGRESS state in beam 2.27

[GitBox <gi...@apache.org>]

damccorm opened a new issue, #20713:
URL: https://github.com/apache/beam/issues/20713

   *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.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org