You are viewing a plain text version of this content. The canonical link for it is here.

Posted to builds@streampark.apache.org by GitBox <gi...@apache.org> on 2026/10/16 09:11:47 UTC

[GH] (streampark/fix/issue-4338-savepoint-state): Workflow run "Frontend" failed!

The GitHub Actions job "Frontend" on streampark.git/fix/issue-4338-savepoint-state has failed.
Run started by GitHub user zhang-arvin (triggered by zhang-arvin).

Head commit for run:
4f4746baf8d2f36aa7065c19a531df0e7d844de7 / 张万义 <zh...@163.com>
[fix] Fix savepoint state stuck in SAVEPOINTING after savepoint completion

Fixes #4338: When manually triggering a savepoint, the release status
remains in WAITING/SAVEPOINTING state even after the savepoint completes.

Root cause:
1. DeflaterUtils.unzipString() throws IllegalArgumentException when
   flinkConf is not valid Base64 (e.g., stored as plain file path),
   which propagates up and causes savepoint saving to fail.
2. FlinkCheckpointProcessor.process() does not clean the SAVEPOINT_CACHE
   when saveSavepoint() throws an exception, causing the state to remain
   stuck in SAVEPOINTING.

Changes:
1. DeflaterUtils.unzipString(): catch IllegalArgumentException from
   Base64.getDecoder().decode() and return null gracefully.
2. FlinkCheckpointProcessor.process(): wrap saveSavepoint() in try-finally
   to ensure cleanSavepoint() is always called.
3. FlinkEnv.convertFlinkYamlAsMap() and getFlinkConfig(): handle null
   return from unzipString() gracefully, returning empty map/properties.

Report URL: https://github.com/apache/streampark/actions/runs/35077982222

With regards,
GitHub Actions via GitBox