DanielLeens opened a new pull request, #11557: URL: https://github.com/apache/seatunnel/pull/11557
## Purpose Start the first reviewable Phase 0 slice of the managed Source runtime work without changing connector execution semantics. This PR establishes the measurements needed to decide which readers can safely move to a future engine-managed mailbox. ## Changes - add source-scoped poll totals, wall time, maximum time, and a diagnostic 5 ms soft-budget counter - measure reader control callbacks that currently occupy Hazelcast operation threads - split Source checkpoint timing into checkpoint-lock wait, reader snapshot/state registration, and barrier ACK/forward stages - keep cumulative and maximum metrics in a bounded-cardinality internal aggregator - document every metric and its exact timing boundary in English and Chinese - add deterministic tests for threshold boundaries, cumulative values, independent checkpoint stages, and monotonic maximums ## Compatibility and performance - legacy SourceReader callback order, checkpoint state, serialization, configuration defaults, and connector SPI are unchanged - engine observability remains disabled by default; when disabled, the new metrics are not registered and the hot path only evaluates the existing null guard - when observability is enabled, poll timing reuses the existing `System.nanoTime()` sample; the incremental cost is bounded counter updates - the 5 ms budgets are diagnostic only and never interrupt or move a legacy connector to another execution lane ## Validation - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -f seatunnel-api/pom.xml spotless:apply` - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -f seatunnel-api/pom.xml spotless:check` - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -f seatunnel-engine/seatunnel-engine-server/pom.xml spotless:apply` - `./mvnw -nsu -Dmaven.gitcommitid.skip=true -f seatunnel-engine/seatunnel-engine-server/pom.xml spotless:check` - local compilation and tests were intentionally not run; the current PR head's GitHub CI is the functional verification authority ## Follow-up scope This draft intentionally does not introduce the mailbox, Lane A allowlist, command protocol, runtime checkpoint metadata, or connector migration. Those remain separate Phase 0/Phase 1 review gates after the measurements in this PR are accepted. -- 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]
