Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Good day
We are trying to load a big table from on-premises to AWS Kinesis.
At some point during the initial full load, we get the following errors and the table is reloaded.
03449616: 2026-04-14T07:05:29 [TARGET_LOAD ]E: Failed to produce kinesis message with record id <663349006> to partition <0> in stream 'xxx'. : Encountered network error when sending http request [1022601] (queue_utils.c:120)
03449616: 2026-04-14T07:05:29 [TARGET_LOAD ]E: Failed to send message [1022601] (queue_utils.c:1877)
03449616: 2026-04-14T07:05:29 [TARGET_LOAD ]E: Failed to produce message. [1022601] (queue_load.c:74)
03449544: 2026-04-14T07:05:29 [TASK_MANAGER ]I: Task error notification received from subtask 1, thread 1, status 1022601 (replicationtask.c:3653)
03449616: 2026-04-14T07:05:29 [TARGET_LOAD ]E: Error executing data handler [1022601] (streamcomponent.c:2034)
03449616: 2026-04-14T07:05:29 [TASK_MANAGER ]E: Stream component failed at subtask 1, component st_1_xxx [1022601] (subtask.c:1506)
03449616: 2026-04-14T07:05:29 [TARGET_LOAD ]E: Stream component 'st_1_xxx' terminated [1022601] (subtask.c:1675)
03449544: 2026-04-14T07:05:33 [TASK_MANAGER ]I: Subtask #1 ended (replicationtask_util.c:591)
03449544: 2026-04-14T07:05:33 [TASK_MANAGER ]I: Reloading table 14 because subtask #1 finished with error (replicationtask.c:2761)
I've already added the following internal parameters:
resultsWaitMaxTimes : 3000
resultsWaitTimeoutMS : 2500
Task settings: Commit rate during full load = 150000
There is no throttling on the Kinesis side.
I suspect it might be either a break in the network or slow response.
Running Qlik Replicate V2025.5.0.134 on Microsoft Windows Server 2019 Standard
Any suggestions on what other parameters I can set to do retries / wait longer, instead of reloading from start?
Thanx
Hello @sanlamZA ,
We have a similar article, see Failed to produce kinesis message:
I'm pasting the contents here:
The number of messages and size of messages outputted to the Kinesis Target can be controlled with the following Internal Parameters for the Kinesis Target:
maxMessagesInBatch
maxBatchSize
Please review your CloudWatch for metrics and limit output accordingly.
https://aws.amazon.com/premiumsupport/knowledge-center/kinesis-readprovisionedthroughputexceeded/
Hope it helps.
John.
Hello @sanlamZA ,
We have a similar article, see Failed to produce kinesis message:
I'm pasting the contents here:
The number of messages and size of messages outputted to the Kinesis Target can be controlled with the following Internal Parameters for the Kinesis Target:
maxMessagesInBatch
maxBatchSize
Please review your CloudWatch for metrics and limit output accordingly.
https://aws.amazon.com/premiumsupport/knowledge-center/kinesis-readprovisionedthroughputexceeded/
Hope it helps.
John.
Thanx, John. I'll investigate and test / play around 🙂
Thank you for your support! @sanlamZA