tomatotomata commented on PR #11602: URL: https://github.com/apache/seatunnel/pull/11602#issuecomment-5186345685
I pushed `e4bdab3` with the final-history boundary you described. - Realtime `getCurrJobMetrics` remains best-effort and keeps the 3-second worker budget. - Terminal history now uses a strict collection path. A timeout, inactive worker, missing member, interruption, or other worker error aborts the snapshot before persistence. - `subPlanDone` retries that failure and leaves task-group context intact, so a later attempt can collect the complete result. The history write and context cleanup still happen together only after a successful collection. - Added a focused `JobMasterTest` that simulates a worker timeout and verifies finished metrics are not stored. `git diff --check` passes. I could not execute the SeaTunnel test module locally because this sparse checkout cannot resolve the required snapshot parent artifacts, and the full reactor stops earlier in the shaded config module. The branch is pushed so the repository CI can exercise the supported build path. Let me know if you would rather have the strict collector return an explicit completeness result instead of failing the cleanup retry path. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
