Overview
Version
| FineDataLink Version | Function Description |
|---|---|
| 4.1.1 | Allowed setting scheduling dependencies for scheduled tasks. Masked tasks that might form a loop in the drop-down list of Task Dependency. |
| 4.1.4 | Added a View Example button to the Event-Based Scheduling tab page to help you understand the function. You could click it to view examples. |
| 4.1.11.1 | Optimized the Event-Based Scheduling function:
|
| 4.1.13.1 | Redirected you to the O&M Center > Scheduled Task > Scheduling Plan > Event-Based Scheduling page automatically after you opened a scheduled task in Production Mode and chose Scheduling Plan > Event-Based Scheduling > View. The event-based scheduling plan of the task would be displayed. |
Application Scenario
Task A, Task B, and Task C that run independently exist on the ODS layer. Task D and Task F exist on the DW layer. Task D is required to run after Task A and Task B are executed to reduce the time waiting for the whole ODS layer to be updated. Task D will not be triggered if Task A and Task B fail, thus avoiding data accuracy issues.
In a scheduling plan, Task B is set to depend on Task A. If you want to avoid resource strain, you can set Task A to be executed in the morning and set Task B to be executed in the evening (idle time) instead of immediately after the upstream Task A is completed.
The execution results of Task A trigger the execution of Task B. You do not want Task B to be triggered when Task A fails and is retried.
Function Overview
You can set scheduling dependencies for tasks in FineDataLink. For example, set Task C and subsequent tasks to be executed after Task A and Task B are executed successfully with the specified condition met.
Prerequisite
Ensure you have registered the Scheduling Plan - Advanced Function (Trial) function point before use.
Upgrade Compatibility
After the upgrade, all tasks with dependencies are configured with the same event-based scheduling plan that covers all these tasks. By default, Timing of Judgement of the current task is set to Real-Time Judgment, and the upstream instance can be judged repeatedly when the execution condition involves multiple tasks.
Note: Function Description
Entry of Event-Based Scheduling Plan Adding
Entry One:
You can add an event-based scheduling plan under O&M Center > Scheduled Task > Scheduling Plan > Event-Based Scheduling, as shown in the following figure.
Entry Two:
Open a scheduled task and click the button. Click Event-Based Scheduling and Create to be redirected to Event-Based Scheduling under O&M Center > Scheduled Task > Scheduling Plan. Add an event-based scheduling plan, as shown in the following figure.
Description of the Event-Based Scheduling Plan
| Attribute | Description |
|---|---|
| Current Task Information | It displays the tasks to be scheduled. You can add tasks and delete the tasks you add. When adding tasks, you can only select the published tasks that have not been configured with any event-based scheduling plan. |
| Upstream Task Information | It displays tasks to be executed ahead of the current task. You can add tasks, delete the tasks you add, and select multiple tasks. When adding tasks, you can only select the published tasks that have not been configured with any event-based scheduling plan. When adding tasks, you cannot select tasks whose task dependency or invocation can form a loop. |
| Execution Condition of Current Task Group |
Triggering logic: When the set execution time of the current task is reached, the system judges whether the latest running record of the upstream task meets the condition. If so, the current task will be executed. If not, the current task will not be executed. When the execution of the upstream task meets the set condition, the current task will be executed at the set execution time.
If you tick this option, each running record of the upstream task will be judged only once. The current task will be executed only when all upstream tasks generate the latest running records that meet the condition and have not triggered the execution of the current task. If you do not tick this option, the running record of the upstream task can be judged repeatedly. The latest running record can be reused for judgment.
|
| Downstream Task Information | It displays tasks to be executed after the current task is successfully executed. You can add tasks and delete the tasks you add. |
Management of the Event-Based Scheduling Plan
You can manage the added event-based scheduling plans under O&M Center > Scheduled Task > Scheduling Plan > Event-Based Scheduling. For details, see Scheduled Task O&M - Scheduling Plan.
Starting from FineDataLink 4.1.13.1, after you open a scheduled task in Production Mode, click the button, and choose Event-Based Scheduling > View, you will be redirected to the Event-Based Scheduling tab page under O&M Center > Scheduled Task > Scheduling Plan, on which the event-based scheduling plan of the task is displayed, as shown in the following figure.
Other Functions of Event-Based Scheduling
1. Manual Running
In the production environment, you can click the Run Current Task and Downstream Item button. The generated running record determines whether to trigger the execution of the downstream tasks based on the task relation and Condition Content configured in Event-Based Scheduling, as shown in the following figure.
Note:The running record generated by manual task execution (including the downstream instances pulled by this execution) is judged according to the condition in the event-based scheduling plan (which is also valid for Timed Judgment). If the execution of downstream tasks is successfully triggered, this running record will not be used for judgment.
2. Running Record After Retry
You can select Retry Current Task and Downstream Item when retrying the current task. The generated running record determines whether to trigger the execution of downstream tasks based on the task relation and Condition Content configured in Event-Based Scheduling.
Application scenario: Task A and Task B are upstream tasks of Task D. If both tasks run successfully, the execution of Task D will be triggered. You may want to rerun Task A and Task B when both tasks fail. In this case, you can use this function.
For details about the Retry function, see Scheduled Task O&M - Running Record.
提示:3. Permission
You can view an event-based scheduling plan if you have Management permission on any task in this plan. However, you cannot move or delete tasks already on the canvas or tasks on which you lack Management permission.
You can only configure triggering conditions for tasks on which you have Management permission. If a task group contains tasks beyond your permission scope, you cannot adjust its triggering conditions, or add/delete its upstream/downstream tasks. You can move tasks within your permission scope to a new group.
You cannot edit upstream/downstream groups (such as moving and deleting tasks) in an event-based scheduling plan if these groups contain a task beyond your permission scope.
Special Scenario Description
| Scenario | Description |
|---|---|
Task D depends on Task C, Task C depends on Task B, and Task B depends on Task A. Tasks A, B, C, and D belong to Group One, Group Two, Group Three, and Group Four, respectively. Now, Task B has been deleted. Task C has been configured with a timed scheduling plan separately. | Case one: If Group Two contains other tasks, the entire event-based scheduling plan will not be affected and will pass the validation. Case two: If Group Two does not contain other tasks, the entire event-based scheduling plan will be marked red in the management list. Validation failure will be displayed on the event-based scheduling editing page, and the scheduling status of this plan will be exception. The entire event-based scheduling plan will be invalid, and the execution result of Task C will not trigger the execution of Task D. |
Procedure
For example, you have created tasks on ODS, DW, and DM layers, as shown in the following figure.
You want to configure a timed scheduling plan for the tasks on the ODS layer. You want to configure an event-based scheduling plan for tasks on the DW and DM layers, and want the tasks on the DW and DM layers to be executed after the tasks on the ODS layer are successfully executed with the specified conditions met.
Adding an Event-Based Scheduling Plan
Choose O&M Center > Scheduled Task > Scheduling Plan, click Event-Based Scheduling, and add an event-based scheduling plan, as shown in the following figure.
Select the current task of the event-based scheduling plan, which is the task on the DW layer that needs to be scheduled, as shown in the following figure.
Setting Current and Upstream Task Information
Enter the editing page, click Group in Current Task Information, and rename it DW. Similarly, change the group name in Upstream Task Information to ODS. Add the tasks on the ODS layer to Upstream Task Information, as shown in the following figure.
Configuring the Execution Condition of the Current Task Group
Configure Execution Condition of Current Task Group by ticking Timed Judgment and configuring the execution time and the condition content for the current task, as shown in the following figure.
Setting Downstream Task Information
Set the task on the DM layer as the downstream task, which will be executed after the current task is executed according to the event-based scheduling plan, as shown in the following figure.
Go back to the event-based scheduling page, as shown in the following figure.
Effect Display
Configure a timed scheduling plan for the tasks on the ODS layer. Note that if Timing of Jugement in the event-based scheduling plan is set to Timed Judgment, the start time of this timed scheduling plan needs to be earlier than that set in Timed Judgment, as shown in the following figure.
After the tasks on the ODS layer run successfully, the task on the DW layer will be executed at the scheduled time according to the event-based scheduling plan. If the task on the DW layer runs successfully, the downstream task on the DM layer will be executed after real-time judgment, as shown in the following figure.
Previous：Timed Scheduling
