IBM i blocking snapshots: verify the pause handshake after request acceptance
Request acceptance, streaming pause acknowledgment and snapshot execution are separate states.
The distance between acceptance and execution
Request acceptance, streaming pause acknowledgment and snapshot execution are separate states. Do not display startup or completion from a request log alone. Supply Truthound with distinct request and execution records; counting accepted requests as executed work can hide a recovery extraction that never began. [1, 2, 3]
Blocked before the query
Debezium #3007 reports blocking snapshots accepted but never started on the incubating IBM i 3.5.0.Final connector because the streaming pause handshake is absent. Main was inspected in source, and complete logs were not attached. This differs from the related member-scope report: execution stalls before the snapshot query, so no output is not an established empty result. [1]
Join states by signal
Track acceptance, pause acknowledgment, actual startup and output scope by signal ID. Exclude unexecuted requests from completion lists. Use an approved signal on a streaming connector whose initial snapshot has finished, and keep cancellation or permission rejection distinct rather than requiring every request to start. [1, 3]
What startup 1 establishes
The illustrative approved request blk-1 requires snapshot startup after pause acknowledgment. Expected startup is 1. Observed 1 meets only that startup condition; 0 remains unexecuted. Row coverage and completion still need separate evidence. The fixture is not an operating connector log. [1, 3]
Check prepared phase observations
Truthound Core Python SDK 3.3.2 can compare prepared required_snapshot_started and observed_snapshot_started through ColumnPairValidator with relationship="==". The operator maps signals to phase logs, producing non-missing states and retaining missing observations separately. The SDK does not pause the journal loop or implement the handshake. [1, 2, 3]
The requester’s completion condition
Use a supported separate extraction procedure or test a version with the handshake in isolation. Rejected and cancelled requests are outside the expected-startup 1 fixture. After startup is confirmed, verify the additional-condition filter and source keys before announcing the requested extraction complete. [1, 3]
Application conditions
Use an approved signal on an already streaming connector and distinguish request logs from phase execution.
Alternatives
Choose a supported separate extraction or isolate-test a handshake correction.
Limitations
The SDK does not pause the journal loop or implement the handshake; startup alone does not prove complete rows.
Evidence
- Event checked
- Subject checked
- Modified
