yigitcan-ozturk commented on issue #12442: URL: https://github.com/apache/seatunnel/issues/12442#issuecomment-5886359428
Hi, I'd like to take this issue. I checked the current thread and matching PR search and do not see an active implementation PR for #12442. I will keep the first change focused on the failure boundary Daniel described: wrap the scheduled checkpoint-trigger body so an unexpected failure cannot disappear in an unobserved scheduled future, emit the failure through the SeaTunnel engine logger with job id, pipeline id, and checkpoint type, and route it through an explicit coordinator/job error path rather than blindly re-arming arbitrary Throwables. Before changing behavior, I'll trace the existing coordinator error propagation on current dev and use the smallest compatible failure policy. The regression coverage will force a failure before either re-arm point, verify that it becomes visible to the coordinator/job error path with context, and verify that the ordinary pending/min-interval re-arm paths remain unchanged. Please let me know if this focused scope is available; if so I'll proceed against dev and link the PR here. -- 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]
