Skip to main content
Announcements
UPGRADE ADVISORY for Qlik Replicate 2024.5: Read More
cancel
Showing results for 
Search instead for 
Did you mean: 
Preethi13
Contributor II
Contributor II

Tasks while restarting services

Hi 

Quick question, what happens to the tasks running when we restart all 3 services - qlik replicate, replicate UI and QEM. Do they have an interruption that is do they get stopped and resumed.  

Thank you

Labels (1)
2 Solutions

Accepted Solutions
Dana_Baldwin
Support
Support

Hi @Preethi13 

Restarting the QEM service only impacts QEM, it will not be available while it is offline.

Restarting the Replicate UI service only impacts the user interfaces - users will not be able to use the tool while it is offline.

Restarting the Replicate server service will stop all running tasks. Starting the service will resume the tasks that were running when it was asked to stop.

Please note:

If any of the tasks timed out while stopping (would be indicated on screen of the task and in the repsrv.log: "Task 'Task Name' stop timeout occurred. The task will be terminated"), then start the task(s) that timed out by timestamp, taking any latency plus a buffer for long running transactions into account when determining the start time. Some duplicate record warnings/errors may be encountered if there is any overlap from where the task stopped reading the source.

Thanks,

Dana

View solution in original post

Preethi13
Contributor II
Contributor II
Author

Thank you for your response. Appreciate it!

View solution in original post

3 Replies
Dana_Baldwin
Support
Support

Hi @Preethi13 

Restarting the QEM service only impacts QEM, it will not be available while it is offline.

Restarting the Replicate UI service only impacts the user interfaces - users will not be able to use the tool while it is offline.

Restarting the Replicate server service will stop all running tasks. Starting the service will resume the tasks that were running when it was asked to stop.

Please note:

If any of the tasks timed out while stopping (would be indicated on screen of the task and in the repsrv.log: "Task 'Task Name' stop timeout occurred. The task will be terminated"), then start the task(s) that timed out by timestamp, taking any latency plus a buffer for long running transactions into account when determining the start time. Some duplicate record warnings/errors may be encountered if there is any overlap from where the task stopped reading the source.

Thanks,

Dana

Preethi13
Contributor II
Contributor II
Author

Thank you for your response. Appreciate it!

georefi
Contributor
Contributor

Look at the history of the task (make sure you enable task history), are you getting any errors?

Run the batch file in a command prompt, do the commands actually work?

Could be permissions for the account you are running the task as