SEZ9 commented on issue #12202: URL: https://github.com/apache/seatunnel/issues/12202#issuecomment-5674153052
Thanks for the detailed trace, and thanks @CryoThrust for offering to help. Agreed with the direction already discussed: no timeout around `join()` until the actual blocking call in `cleanJob()` is identified, and an opt-in instrumentation PR with no default behavior change is the right first step. One thing that would help in the meantime: which SeaTunnel version/commit the failure was observed on. If anyone gets a live reproduction, a `jstack` of the master while the scheduler thread is wedged would also let us tell monitor contention from a stalled IMap operation. Happy to review the PR once it is up. <!-- streview-comment:1061 --> -- 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]
