A customer reported that a pipeline with a output connector configured with a 10-minute output buffering interval stalled input processing for 10 minutes while a checkpoint was running. Changing the output buffering interval to 10 seconds fixed the problem (not reported: whether it stalled input processing for 10 seconds).
The customer initially encountered the issue while using transactions. The customer disabled transactions and the problem persisted.
This problem should not occur, because an in-progress checkpoint waiting for output to flush does not stall the circuit: that wait occurs in the background and allows the circuit to proceed.
The pipeline can stall if the output buffers are full, but in that case there should be a message pipeline stalled {elapsed_secs} seconds because output buffers are full, which the customer did not observe.
This deserves further investigation.
A customer reported that a pipeline with a output connector configured with a 10-minute output buffering interval stalled input processing for 10 minutes while a checkpoint was running. Changing the output buffering interval to 10 seconds fixed the problem (not reported: whether it stalled input processing for 10 seconds).
The customer initially encountered the issue while using transactions. The customer disabled transactions and the problem persisted.
This problem should not occur, because an in-progress checkpoint waiting for output to flush does not stall the circuit: that wait occurs in the background and allows the circuit to proceed.
The pipeline can stall if the output buffers are full, but in that case there should be a message
pipeline stalled {elapsed_secs} seconds because output buffers are full, which the customer did not observe.This deserves further investigation.