nzw921rx opened a new pull request, #13255:
URL: https://github.com/apache/seatunnel/pull/13255

   ### Purpose of this pull request
   
   This contribution to Apache SeaTunnel fixes checkpoint benchmark failures 
after #13015.
   
   `engine_checkpoint_monitor` is no longer persisted, but the benchmark 
fixture still evicts overview samples and reloads them from MapStore. This 
causes validation to fail with `Checkpoint overview was not stored for job ...`.
   
   Changes:
   
   - Remove `checkpointOverviewIncrementalUpdate` and its dedicated workload.
   - Remove the unused overview reload helper and map reference.
   - Keep `checkpointPersistenceTransaction` and `checkpointIdAtomicIncrement`, 
preserving their measured operations and fixed operation counts.
   - Retain counter persistence checks and checkpoint-file readback. Validate 
overview counts, latest checkpoint and history directly in memory.
   - Update the benchmark comments to reflect the current persistence contract.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Benchmark-only: the standalone checkpoint overview benchmark is removed. No 
engine or connector behavior, configuration, API or checkpoint-format changes.
   
   ### How was this patch tested?
   
   On Java 11:
   
   - Reproduced the original `checkpointPersistenceTransaction` failure before 
applying the patch.
   - Clean benchmark-module build and verification passed: 69 tests, 0 
failures, errors or skips.
   - Both remaining checkpoint benchmarks passed forked JMH smoke runs.
   - Confirmed the removed benchmark is absent from the packaged JMH list.
   - Spotless and `git diff --check` passed.
   
   The JMH runs validate correctness and lifecycle; they are not performance 
measurements.


-- 
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]

Reply via email to