You can translate the question and the replies:

Denodo scheduler dependencies

Hi, We are facing the below problem in setting the dependencies in denodo scheduler. Sequence of job - 1.filecheck job - say JOB1 2.JOB2 3.JOB3 4.JOB4 5.Backup job - say JOB 5 Scenario 1: JOB 1 - dont have any dependencies and it should execute at trigger time(7:16) JOB 2 - have dependency with JOB 1 and the trigger time is set as 7:15 but it should be in waiting status from 7:15 and it should start to execute only after the completion of JOB 1 JOB 3 - have dependency with JOB 2 and the trigger time is set as 7:14 but it should be in waiting status from 7:14 and it should start to execute only after the completion of JOB 2 JOB 4 - have dependency with JOB 3 and the trigger time is set as 7:13 but it should be in waiting status from 7:13 and it should start to execute only after the completion of JOB 3 JOB 5 - have dependency with 3 jobs(JOB 2,JOB 3 and JOB 4) but the problem is this job starts its execution even if any of the 2 dependent jobs finished its execution **but not waiting for 3rd job to finish.** - This dependency is not working as expected Scenario 2: JOB 1 - dont have any dependencies and it should execute at trigger time(7:16) All the below jobs have the depencencies with JOB 1 so basically all the below jobs should start at same time after the completion of JOB 1 but any one of the jobs are still in waiting. For example: JOB 2 - have dependency with JOB 1 and the trigger time is set as 7:15 but it should be in waiting status from 7:15 and it should start to execute only after the completion of JOB 1 JOB 3 - have dependency with JOB 1 and the trigger time is set as 7:15 but it should be in waiting status from 7:15 and it should start to execute only after the completion of JOB 1 JOB 4 - have dependency with JOB 1 and the trigger time is set as 7:15 but it should be in waiting status from 7:15 and it should start to execute only after the completion of JOB 1 - **This is not working as expected** - this job keep on in waiting status even after the completion of dependency job (JOB1) We find some kind of dependencies are not working as expected Please let us know the solution or best approach to have the dependencies. Thanks, Jayasree
user
05-08-2020 06:55:15 -0400

3 Answers

Hi, I scheduled the job with the same dependencies and similar trigger times mentioned in Scenario 1 and 2 and it worked as expected. For Scenario 1, I assume you had the trigger time set for Job 5 as well, for example : 7:12. As per the Scenario 1 description, Job 4 is dependent on Job 3 and Job 3 is dependent on Job 2. So, Job 4 will execute only if both Job 3 and 2 executions are complete. Can you try with the case when Job 5 is dependent on Job 4 only and validate if it waits for Job 4 to finish or execute before that? For the second scenario, I would advise you to check the Scheduler logs to see if there are any kind of errors on why the job did not execute. It is also important to note that if it’s a clustered server, the clocks of all the machines where the instances of the Scheduler server are running must be synchronized using some form of time-sync service. You can refer to the [“Cluster Settings”](https://community.denodo.com/docs/html/browse/latest/scheduler/administration/administration/server_configuration/server_configuration_sections#cluster-settings) section of Scheduler Server Configuration for more information. If you think your settings are correct and still not able to get the expected results, then you can submit a case if you have a valid support account and the support team can take a deeper look into this. Hope this helps!
Denodo Team
05-08-2020 17:32:03 -0400
Hi, Thanks for your suggestion. For Scenario 1, you suggested as below: Can you try with the case when Job 5 is dependent on Job 4 only and validate if it waits for Job 4 to finish or execute before that? If we give JOB 5 is dependent on JOB 4 then any one of the dependencies is not working like at first run, JOB 3 dependencies are not working and in subsequent run the one or other dependencies are not working and changing the status to "WAITING" though the dependent job completed successfully.
user
06-08-2020 00:58:56 -0400
Hi, As explained in the documentation [“Dependencies among Jobs”](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/creating_and_scheduling_jobs/configuring_new_jobs/dependencies_among_jobs#dependencies-among-jobs), if Job A depends on Job B, then Job A should be scheduled to be the first job to be executed ( Job A starts at time X and Job B starts at time x+1 second). Then, “A” will be in WAITING state until “B” completes its execution (note that if “B” is already being executed when “A” starts, then “A” will be in WAITING state until “B” starts a new execution and finishes it). For most of your configured jobs, you are seeing correct behaviour and with the same logic/configuration, the other jobs should work the same way. I would recommend you check the update you currently have and if you are using an old update, then install the latest update as it contains several bug fixes and enhancements. You can download the update from[ “Denodo Support Site”](https://support.denodo.com/) if you are a customer with a valid support account. Apart from that, if you notice that the behaviour is different from what is expected even with the correct configuration and the latest update, then you can submit a case if you have a valid support account. The agent can look into the configuration in place in order to find the reason for this behaviour. For more information on how to create and schedule jobs please refer to the [“Creating and Scheduling Jobs”](https://community.denodo.com/docs/html/browse/7.0/scheduler/administration/creating_and_scheduling_jobs/creating_and_scheduling_jobs#creating-and-scheduling-jobs) section of the Scheduler Administration Guide. Hope this helps!
Denodo Team
07-08-2020 13:00:08 -0400
You must sign in to add an answer. If you do not have an account, you can register here