abdessalems commented on issue #11679: URL: https://github.com/apache/seatunnel/issues/11679#issuecomment-5230272931
Thanks @loustler. I was able to reproduce the hang in CI and capture thread dumps from both the engine and the seatunnel.sh client. The client is stuck in CompletableFuture.get(), waiting for a result that never arrives. The interesting part is on the engine side: one coordinator thread is holding the SubPlan lock while waiting in startedLatch.await(), while another thread is blocked trying to enter updatePipelineState() to handle the checkpoint error. So it looks like the client is just a symptom here. The pipeline never reaches its terminal state because of the engine-side lock/wait. -- 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]
