DanielLeens commented on issue #12382: URL: https://github.com/apache/seatunnel/issues/12382#issuecomment-5892209120
Classification: A / Connector-V2 PostgreSQL CDC restore-delivery integrity. Thank you for the disciplined comparison. Thirty runs on each recorded revision, with the real Zeta savepoint -> restore -> post-reattachment insert and no lost `id=15` result in either 29-run reached sample, materially weakens the current loss hypothesis. The result is not a confirmation that the original report is fixed: the observed zero-event upper bound is still 9.8% per revision, the original scheduled failure remains unexplained, and the agent instrumentation can change timing. Please keep this as an investigation, not a production-fix path. The next useful evidence is an uninstrumented control on the same two revisions, then a separately recorded controlled-load matrix if it is needed. For every run, retain the reached/not-reached count and keep the pre-restore slot/committed-LSN setup timeout distinct from the delivery assertion. Only if the row loss becomes reproducible should test-only correlation trace the WAL handoff, reader emission/checkpoint advancement, and JDBC-sink receipt. No production tracing or fix PR is justified yet. No label or assignment change in this pass. -- 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]
