Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
jskw
Contributor
Contributor

Issue in the replication process [TARGET_LOAD ]E: Time out occured while trying to empty slots on Message Tracker. [1020414] (queue_utils.c:214)

Dear Support,

We are trying to replicate data from the SAP HANA source in the GCP to Kafka target in the AWS. Approximately 5 minutes after the initiation of replicating data to Kafka brokers in AWS, the Qlik produces the Kafka: Message delivery failed: Local: Message time out error. , but the task manager keeps producing the following errors:

[TARGET_LOAD ]E: Time out occured while trying to empty slots on Message Tracker. [1020414] (queue_utils.c:214)

[TARGET_LOAD ]E: Failed to send message [1020414] (queue_utils.c:1276)

[TARGET_LOAD ]E: Failed to produce message. [1020414] (queue_load.c:74)

[TARGET_LOAD ]W: rdkafka error: (code=-192) 'Local: Message timed out'. Replicate status: 1020414 (kafka_client.c:159)

 

Kindly appreciate your help.

Thanks.

 

 

 

1 Reply
SwathiPulagam
Support
Support

Hi,

Messages which are currently in delivery and waiting for ACK are tracked in what we call MessageTracker. Once there are more than X messages waiting for ACK, Replicate will keep waiting some additional time before failing with this error mentioned above.

 

 The relevant parameters are:

 

 “resultsWaitTimeoutMS" - time to wait

"resultsWaitMaxTimes" - how many retries

 

i.e.:

 If resultsWaitTimeoutMS is 500 and resultsWaitMaxTimes is 1000, the client will wait 500x1000 ms.

 

You will need to tweak those parameters according to the load - that means that you have to increase them, in a "trial and error" manner until this error is not encountered.

  

=====

from the Kafka target endpoint

You can  try to set the internal parameter : 

Open the Kafka endpoint, click on the Advanced tab.

Click on "Internal parameters"

resultsWaitTimeoutMS (default 500)

metadataTimeoutMS (5000)

confirmIntervalMaxTimeMS (1000)

resultsWaitMaxTimes (500)

 

Try to double or triple their default value

 

Notes that when changing any endpoint setting, tasks need to stop and resume for the new setting to take.

 

Thanks,

Swathi