Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jun 7, 2022 12:59:30 PM
May 30, 2022 11:45:14 AM
The Longer than (seconds) parameter is used to determine how long to wait for the change capture to become quiescent so that we can upload what we have captured. We can refer to this as the CDC Idle Timeout.
The But less than (seconds) parameter is used to determine the maximum amount of time to wait before sending what is ready, regardless of if the CDC Idle Timeout has been reached.
The Force apply a batch when processing memory exceeds (MB) parameter is used to determine the maximum amount of data to build up in a batch before sending, regardless of the two time based parameters.
Usage scenarios:
The settings come down to what the latency requirements are and the speed in which the target can accept batches. If the target can handle small batches efficiently then the default values are usually used. If the target prefers large batches (Teradata, Vertica, Greenplum, Snowflake) then increasing the size of the ‘Longer than…’ and ‘Force apply…’ parameters can be tuned based on the speed of the transfer to the target.
Transactions can be cached to disk in swap files (.tswp) in the ..\data\tasks\TASK_NAME\sorter folder if there are large or long running transactions on the source, or if the target cannot keep up with the data being sent. The Transaction Offload Tuning settings determine when changes are cached to disk, when reaching the size or duration values set, whichever comes first.
so if I want my task to apply the changes captured in last 30 mins only. just like scheduling every 30 mins unless processing memory reach then waht should be longer than and less than seconds @Steve_Nguyen
Hello @kishetty03
Please post your query in the Qlik Replicate forum, indicating your requirements and what you are attempting to achieve. You will have access to our active community and support engineers in this forum.
All the best,
Sonja