DanielLeens commented on issue #11013: URL: https://github.com/apache/seatunnel/issues/11013#issuecomment-4696883287
Thanks — this is enough useful evidence for the issue to stay actionable. With the newer single-split reproduction, the problem is no longer just "the job kept running" in a broad sense. The combination of: - one split - `startup.mode = initial` - snapshot start being logged - downstream rows stalling far below the source count - `resolvedTs` and checkpoints continuing to advance still points much more strongly to a real reader-side bug in the snapshot-to-stream handoff / row-flush path than to a monitoring illusion. So from my side, no additional generic information is required right now just to keep this issue open. The logs and count SQL you preserved are already valuable enough for someone preparing a deterministic regression test or a fix PR. If a contributor starts working on the fix later, the full JobManager / TaskManager logs around this reproduction would still be helpful as follow-up evidence. But this issue already has enough signal to continue tracking as a real bug. -- 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]
