You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@seatunnel.apache.org by "DanielLeens (via GitHub)" <gi...@apache.org> on 2026/06/29 10:44:42 UTC
Re: [PR] [Fix][Zeta] Clean failed pipeline metrics without full-map cleanup scan [seatunnel]
DanielLeens commented on PR #10757:
URL: https://github.com/apache/seatunnel/pull/10757#issuecomment-4831576503
Thanks for the update.
I rechecked the current head `0a2b04395301aa342e9f5b4e98574da93889dd97`, and my source-level conclusion is still the same as in the latest Daniel review: I do not see a reopened blocker in the failed-pipeline cleanup path (`JobMaster.enqueuePipelineCleanupIfNeeded(...)` -> `CoordinatorService.submitJob(..., isStartWithSavePoint=true)` -> `cleanupPendingPipelineCleanupForRestore(jobId)` -> `PipelineCleanupRecord.mergeFrom(...)`).
At the moment the remaining gate is still CI rather than a new code issue from this path. The aggregated `Build` check on this head is still red, so I am still waiting on that signal instead of asking for another code change from the cleanup logic itself.
--
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: commits-unsubscribe@seatunnel.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org