Timed scheduling task system, method, device, server and readable storage medium

Abstract

The present invention relates to the field of data processing technology, and discloses a timed scheduling task system, method, device, server, and readable storage medium. The system includes a local data server and a remote data server, wherein a second timed scheduling task on the remote data server is configured consistent with a first timed scheduling task on the local data server. The remote data server is configured to pull and trigger the second timed scheduling task, which is configured consistent with the first timed scheduling task, when the local data server fails. By implementing the present invention, service switching of timed scheduling tasks is avoided when a local data server fails, ensuring the continuity and timeliness of timed scheduling task execution.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a timed scheduling task system, method, device, server and readable storage medium. Background Art

[0002] The importance of scheduled scheduling services in the FinTech sector is self-evident. These services include the scheduled closing of transaction orders, the scheduled clearing of transaction data, and the scheduled summary and reporting of cleared data. As an internal service not subject to inter-system interaction, scheduled scheduling services, when the data center's scheduling service is unavailable, most business scenarios can only wait for the scheduling service to be restored and re-trigger scheduled tasks. For businesses requiring time-sensitive processing, service switching through business interfaces or synchronization of business database tables can ensure business continuity. However, requiring the business to perform service switching increases access costs, and business interfaces fail to truly achieve service decoupling. This undoubtedly increases the complexity of business operations and may still affect business continuity. Summary of the Invention

[0003] In view of this, the embodiments of the present invention provide a timed scheduling task system, method, device, server and readable storage medium to solve the problem of high access cost and complex operation of triggering timed scheduling tasks on time when the scheduling service of the data center is unavailable.

[0004] According to the first aspect, an embodiment of the present invention provides a timed scheduling task system, including: a local data server, used to pull a first timed scheduling task and trigger the first timed scheduling task; an off-site data server, which is communicatively connected to the local data server, and the off-site data server is configured with a second timed scheduling task, and the configuration of the second timed scheduling task is consistent with the configuration of the first timed scheduling task of the local data server; the off-site data server is used to pull and trigger the second timed scheduling task that is consistent with the configuration of the first timed scheduling task when the local data server fails.

[0005] In combination with the first aspect, in the first embodiment of the first aspect, the local data server includes: a scheduling service interface, which is communicatively connected to the remote data server, and is used to send a pull instruction to the remote data server when the local data server fails, so that the remote data server pulls the second scheduled task based on the pull instruction.

[0006] In combination with the first aspect, in the second embodiment of the first aspect, the local data server includes: a management control interface, which is communicatively connected to the remote data server, and is used to send a trigger instruction to the remote data server when the local data server fails, so that the remote data server triggers the second timed scheduling task based on the trigger instruction.

[0007] In combination with the first aspect, in a third implementation of the first aspect, the local data server sends status parameters to the remote data server at preset time intervals, and the status parameters include heartbeat data.

[0008] In combination with the third implementation of the first aspect, in the fourth implementation of the first aspect, the remote data server determines whether a failure occurs in the operation of the local data server based on the status parameter.

[0009] According to the second aspect, an embodiment of the present invention provides a method for executing a scheduled task, which is used for the scheduled task system described in the first aspect or any embodiment of the first aspect, and the method includes the following steps: obtaining the working status of a local data server, and the local data server is used to pull and trigger a first scheduled task; judging whether the working status is in a fault state; when the working status is in a fault state, controlling the remote data server to pull and trigger a second scheduled task that is consistent with the configuration of the first scheduled task.

[0010] In combination with the second aspect, in the first implementation of the second aspect, the method also includes: when the local data server is not in the fault state, the local data server sends status parameters to the remote data server at preset time intervals, and the status parameters include heartbeat data; the remote data server receives the status parameters and determines whether to pull and trigger the second timed scheduling task based on the status parameters.

[0011] In combination with the second aspect, in the second implementation of the second aspect, before determining whether the working status is in a fault state, the method also includes: obtaining the running status of the first timed scheduling task; determining whether the running status of the first timed scheduling task is in an on state; when the running status of the first timed scheduling task is in an on state, determining whether the working status of the local data server is in a fault state.

[0012] In combination with the second embodiment of the second aspect, in the third embodiment of the second aspect, the method also includes: when the first scheduled task is not started, controlling the remote data server not to perform the pull operation and trigger operation of the second scheduled task.

[0013] According to the third aspect, an embodiment of the present invention provides an execution device for a timed scheduling task, which is used for the timed scheduling task system described in the first aspect or any embodiment of the first aspect, and the device includes: an acquisition module, used to obtain the working status of a local data server executing a first timed scheduling task; a judgment module, used to judge whether the working status is in a fault state; and a startup module, used to control the remote data server to pull and trigger a second timed scheduling task that is consistent with the configuration of the first timed scheduling task when the working status is in a fault state.

[0014] According to the fourth aspect, an embodiment of the present invention provides a server, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the method for executing the timed scheduling task described in the second aspect or any embodiment of the second aspect by executing the computer instructions.

[0015] According to the fifth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute the method for executing a timed scheduling task described in the second aspect or any embodiment of the second aspect.

[0016] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects:

[0017] The timed scheduling task system, method, device, server and readable storage medium provided by the present invention pulls a first timed scheduling task and triggers the first timed scheduling task through a local data server. When a local data server fails, the remote data server is controlled to pull and trigger a second timed scheduling task, wherein the configuration of the second timed scheduling task by the remote data server is consistent with the configuration of the first timed scheduling task by the local data server. Thus, service switching of the timed scheduling task is avoided when the local data server fails, thereby reducing the operational complexity of the timed scheduling task and avoiding an increase in access costs. By configuring the timed scheduling task of the remote data server and the timed scheduling task of the local data server in a consistent manner, the continuity of the execution of the timed scheduling task is guaranteed, thereby ensuring the timeliness of the execution of the timed scheduling task. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0019] Figure 1 is a structural block diagram of a timed scheduling task system according to an embodiment of the present invention;

[0020] Figure 2 is another structural block diagram of a timed scheduling task system according to an embodiment of the present invention;

[0021] Figure 3 is another structural block diagram of a timing scheduling task system according to an embodiment of the present invention;

[0022] Figure 4 is a flowchart of a method for executing a timed scheduling task according to an embodiment of the present invention;

[0023] Figure 5 is another flow chart of a method for executing a timed scheduling task according to an embodiment of the present invention;

[0024] Figure 6 is a structural block diagram of an execution device for a timed scheduling task according to an embodiment of the present invention;

[0025] Figure 7 It is a schematic diagram of the hardware structure of the server provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0026] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present invention.

[0027] As an internal service not subject to inter-system interaction, scheduled scheduling services require that, when the data center's scheduling service is unavailable, most business scenarios must wait for the scheduling service to be restored and re-trigger scheduled tasks. For businesses requiring timeliness, service switching through business interfaces or synchronization of business database tables can ensure business continuity. However, requiring the business to perform service switching increases access costs, and business interfaces fail to truly decouple services, undoubtedly increasing the complexity of business operations and impacting business continuity.

[0028] Based on this, the technical solution of the present invention sets up an off-site data server and makes the configuration of the scheduled scheduling tasks of the off-site data server consistent with the scheduled scheduling tasks of the local data server. When the local data server fails, the off-site data server is started, and the scheduled scheduling tasks are pulled and triggered by the off-site data server, thereby avoiding service switching and ensuring the continuity and timeliness of the execution of the scheduled scheduling tasks.

[0029] According to an embodiment of the present invention, an embodiment of a timed scheduling task system is provided, such as Figure 1 As shown, the scheduled task system includes a local data server 11 and a remote data server 12. The local data server 11 is used to pull and trigger a first scheduled task. The remote data server 12 is in communication with the local data server 11, and the configuration of the second scheduled task on the remote data server 12 is consistent with the configuration of the first scheduled task on the local data server 11. Specifically, if the local data server 11 in the scheduled task system fails, the remote data server 12 is controlled to start pulling and triggering the second scheduled task.

[0030] The scheduled task system provided by this embodiment activates a remote data server when a local data server fails, avoiding service switching for scheduled tasks when the local data server fails. This reduces the operational complexity of scheduled tasks and avoids increased access costs. By ensuring consistent configuration of scheduled tasks on the remote data server and the local data server, the continuity of scheduled task execution is ensured, thereby ensuring the timely execution of scheduled tasks.

[0031] As an optional embodiment, the local data server sends status parameters to the remote data server at preset intervals, and the remote data server can determine whether the operating status of the local data server has failed based on the status parameters regularly sent by the local data server. The status parameters can be heartbeat data, which is a command word that the local data server regularly notifies the remote data server of its related operating status. The heartbeat data can be sent at a certain time interval, such as 10 seconds, 30 seconds, 1 minute, or 5 minutes, etc. This application does not make specific restrictions on this, and those skilled in the art can determine it according to actual needs.

[0032] As an optional implementation, Figure 2As shown, the local data server 11 may include a scheduling service interface 111, which is communicated with the remote data server 12. When the remote data server 12 does not receive the heartbeat data sent by the local data server 11 within a certain time interval, it can be determined that the local data server 11 has failed. At this time, the local data server can send a pull instruction to the remote data server, and the remote data server 12 can connect to the scheduling service interface 111 and pull the second scheduled scheduling task that is consistent with the first scheduled scheduling task configuration being executed on the local data server 11 based on the pull instruction, so that the remote data server 12 executes the second scheduled scheduling task, thereby enabling the remote data server to continue to execute the interrupted first scheduled scheduling task, thereby ensuring the execution continuity and timeliness of the scheduled scheduling task.

[0033] As an optional implementation, Figure 3 As shown, the local data server 11 may also include a management control interface 112. The management control interface 112 is used to communicate with the remote data server 12. When the remote data server 12 does not receive the heartbeat data sent by the local data server 11 within a certain time interval, it can be determined that the local data server 11 has failed. At this time, the local data server can send a trigger instruction to the remote data server, and the remote data server 12 can connect to the management control interface 112 and trigger the second scheduled task that is consistent with the first scheduled task configuration being executed on the local data server 11 based on the trigger instruction, so that the remote data server 12 executes the second scheduled task, thereby ensuring that the remote data server 12 can continue to execute the interrupted first scheduled task, thereby ensuring the execution continuity and timeliness of the scheduled task.

[0034] It should be noted that when the local data server 11 is in normal working condition, the remote data server 12 only needs to maintain a normal communication connection with the local data server 11, and does not perform any pull operation or trigger operation of the second scheduled task, thereby avoiding the addition of additional operations and reducing the operational complexity of the scheduled task.

[0035] According to an embodiment of the present invention, an embodiment of a method for executing a timed scheduling task is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0036] In this embodiment, a method for executing a scheduled task is provided, which can be used in a server, such as a computer system or platform composed of a server. Figure 4FIG. 1 is a flow chart of a method for executing a timed scheduling task according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:

[0037] S21, obtaining the working status of the local data server executing the first scheduled task.

[0038] The local data server is used to pull and trigger the first scheduled task. The local data server can report the data packet corresponding to the working status of executing the first scheduled task to the corresponding database of the local data server in real time. When the local data server is started, the scheduled task system can retrieve the data packet corresponding to the working status of the local data server from the database in real time.

[0039] S22, determining whether the working state is in a fault state.

[0040] The scheduled task system identifies and analyzes the data packets it retrieves corresponding to the operating status of the local data server, thereby performing real-time monitoring of the local data server's operating status and determining whether its operating status is in a faulty state. If the operating status is in a faulty state, step S23 is executed; otherwise, other operations are performed. These other operations may include continuing to monitor the operating status of the local data server, or controlling the remote data server to maintain a connection with the local data server and not performing any pull operations or trigger operations. These operations are not specifically limited here.

[0041] S23, controlling the remote data server to pull and trigger a second scheduled task that is consistent with the first scheduled task configuration.

[0042] The second scheduled task of the remote data server is consistent with the configuration of the first scheduled task of the local data server. When the local data server is in a faulty state while executing the first scheduled task, the scheduled task system can control the remote data server to start the pull task and scheduling task of the second scheduled task, wherein the configuration of the first scheduled task is consistent with the configuration of the second scheduled task. This enables the remote data server to continue executing the scheduled task that the local data server was forced to stop due to a fault, without having to wait for the local data server to recover or perform service switching through the local data server.

[0043] The method for executing a scheduled task provided by the present invention obtains the working status of a local data server. When the working status of the local data server is in a faulty state, it controls the remote data server to pull and trigger a second scheduled task that is consistent with the configuration of the first scheduled task. This avoids service switching of the scheduled task when the local data server fails, thereby reducing the operational complexity of the scheduled task and thus avoiding an increase in access costs. By configuring the scheduled tasks of the remote data server and the local data server in a consistent manner, the continuity of the execution of the scheduled task is guaranteed, thereby ensuring the timeliness of the execution of the scheduled task.

[0044] In this embodiment, a method for executing a scheduled task is provided, which can be used in a server, such as a computer system or platform composed of a server. Figure 5 FIG. 1 is a flow chart of a method for executing a timed scheduling task according to an embodiment of the present invention. Figure 5 As shown, the process includes the following steps:

[0045] S31, obtaining the working status of the local data server executing the first scheduled task. Detailed descriptions refer to the corresponding description of step S21 in the above embodiment, which will not be repeated here.

[0046] S32: Obtain the running status of the first scheduled task.

[0047] The running state of the first scheduled task is the current running state of the first scheduled task. The running state of the first scheduled task can be obtained by detecting the running data on the local data server. When the first scheduled task is started and run on the local data server, the local data server can record its running data.

[0048] S33: Determine whether the running status of the first scheduled task is in the enabled state.

[0049] The scheduled task system can determine the running status of the scheduled task based on the running data of the first scheduled task recorded on the local data server. Specifically, the scheduled task system can detect whether the execution data corresponding to the first scheduled task exists on the current local data server to determine whether the running status of the first scheduled task is in the enabled state. If the first scheduled task is in the enabled state, step S34 is executed; otherwise, step S36 is executed.

[0050] S34, determining whether the working status of the local data server is in a fault state.

[0051] When the running status of the first scheduled task is enabled, it indicates that the local data server can pull and trigger the first scheduled task. After the local data server pulls and triggers the first scheduled task, the scheduled task system can monitor the working status of the local data server executing the first scheduled task in real time to determine whether its working status is normal or faulty. If the working status is faulty, step S35 is executed; otherwise, step S37 is executed.

[0052] S35: Control the remote data server to pull and trigger the second scheduled task that is consistent with the first scheduled task configuration. Detailed descriptions refer to the corresponding step 23 of the above embodiment, which will not be repeated here.

[0053] S36, controlling the remote data server not to execute the pull operation and trigger operation of the scheduled task.

[0054] When the local data server is not in a faulty state, the scheduled task can be executed normally on the local data server. At this time, the scheduled task system only controls the remote data server to maintain a connection with the local data server. The remote data server does not need to perform any pull operations or trigger operations. When the scheduled task is not started, it means that the scheduled task has not reached the trigger time, and it is impossible to determine whether the scheduled task can be executed normally on the local data server. At this time, the remote data server only needs to be controlled to maintain a connection with the local data server. The remote data server does not need to perform any pull operations or trigger operations.

[0055] S37, controlling the local data server to send status parameters to the remote data server at preset intervals, wherein the status parameters include heartbeat data; the remote data server receives the status parameters and determines whether to pull and trigger the second timed scheduling task based on the status parameters.

[0056] The local data server sends status parameters to the remote data server at preset intervals, and the remote data server can determine whether the operating status of the local data server has failed based on the received status parameters. The status parameters can be heartbeat data, which is a command word that the local data server periodically notifies the remote data server of its related operating status. The heartbeat data can be sent at a certain time interval, such as 10 seconds, 30 seconds, 1 minute, or 5 minutes, etc. This application does not make specific restrictions on this, and those skilled in the art can determine it according to actual needs.

[0057] The execution method of the timed scheduling task provided by the present invention obtains the running status of the timed task before judging whether the running status of the local data server is in a fault state to determine whether the timed task is started and whether the local data server is in a fault state when executing the timed task, thereby ensuring the timely startup of the remote data server, ensuring the continuity of the execution of the timed scheduling task, and thus ensuring the timeliness of the execution of the timed scheduling task.

[0058] In this embodiment, a device for executing a timed scheduling task is also provided. The device is used to implement the above-mentioned embodiments and preferred embodiments, and the details already described will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0059] This embodiment provides a device for executing a scheduled task, which is used in the scheduled task system described in the above embodiment. Figure 6 As shown, including:

[0060] The acquisition module 41 is used to acquire the working status of the local data server in executing the first time-scheduled task. Detailed descriptions refer to the corresponding descriptions of the above embodiments, which will not be repeated here.

[0061] The judging module 42 is used to judge whether the working state is in a fault state. Detailed descriptions refer to the corresponding descriptions of the above embodiments, which will not be repeated here.

[0062] The startup module 43 is used to control the remote data server to pull and trigger the second scheduled task that is consistent with the first scheduled task configuration when the working state is in the fault state. Detailed descriptions refer to the corresponding descriptions of the above embodiments, which will not be repeated here.

[0063] The device for executing scheduled tasks provided by the present invention obtains the working status of a local data server. When the working status of the local data server is in a faulty state, it controls the remote data server to start pulling and triggering a second scheduled task. The second scheduled task is configured consistent with the first scheduled task. This avoids service switching of the scheduled task when the local data server fails, thereby reducing the operational complexity of the scheduled task and avoiding an increase in access costs. By configuring the scheduled tasks of the remote data server and the local data server consistently, the continuity of the execution of the scheduled task is guaranteed, thereby ensuring the timeliness of the execution of the scheduled task.

[0064] The execution device of the timed scheduling task in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0065] The further functional description of each of the above modules is the same as that of the above corresponding embodiments and will not be repeated here.

[0066] The embodiment of the present invention further provides a server having the above Figure 6 The execution device of the timed scheduling task shown.

[0067] See also Figure 7 , Figure 7 This is a schematic diagram of the structure of a server provided by an optional embodiment of the present invention. Figure 7 As shown, the server may include: at least one processor 501, such as a CPU (Central Processing Unit), at least one communication interface 503, a memory 504, and at least one communication bus 502. The communication bus 502 is used to realize the connection and communication between these components. The communication interface 503 may include a display screen (Display), a keyboard (Keyboard), and the optional communication interface 503 may also include a standard wired interface and a wireless interface. The memory 504 may be a high-speed RAM memory (Random Access Memory, volatile random access memory) or a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 504 may optionally be at least one storage device located away from the aforementioned processor 501. The processor 501 may be combined with Figure 6 In the described apparatus, the memory 504 stores an application program, and the processor 501 calls the program code stored in the memory 504 to execute any of the above method steps.

[0068] The communication bus 502 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The communication bus 502 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or one type of bus.

[0069] Among them, the memory 504 may include volatile memory (English: volatile memory), such as random-access memory (English: random-access memory, abbreviated: RAM); the memory may also include non-volatile memory (English: non-volatile memory), such as flash memory (English: flash memory), hard disk drive (English: hard disk drive, abbreviated: HDD) or solid-state drive (English: solid-state drive, abbreviated: SSD); the memory 504 may also include a combination of the above types of memory.

[0070] The processor 501 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and a NP.

[0071] The processor 501 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0072] Optionally, the memory 504 is also used to store program instructions. The processor 501 can call the program instructions to implement the application Figure 4 and 5 The execution method of the timed scheduling task shown in the embodiment.

[0073] An embodiment of the present invention further provides a non-transitory computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the processing method of the execution method of the timed scheduling task in any of the above method embodiments. Wherein, the storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory (Flash Memory), a hard disk drive (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above types of memory.

[0074] Although the embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention. Such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A timed scheduling task system, characterized in that: include: A local data server, configured to pull a first scheduled task and trigger the first scheduled task; A remote data server is communicatively connected to the local data server, the remote data server is configured with a second timed scheduling task, and the configuration of the second timed scheduling task is consistent with the configuration of the first timed scheduling task of the local data server; The remote data server is used to pull and trigger the second scheduled task that is consistent with the first scheduled task configuration when the local data server fails; The scheduling service interface is in communication with the remote data server and is used to send a pull instruction to the remote data server when the local data server fails, so that the remote data server pulls the second timed scheduling task based on the pull instruction.

2. The system according to claim 1, wherein: The local data server includes: A management control interface is connected to the remote data server for sending a trigger instruction to the remote data server when the local data server fails, so that the remote data server triggers the second timed scheduling task based on the trigger instruction.

3. The system according to claim 1, wherein: The local data server sends status parameters to the remote data server at preset intervals, where the status parameters include heartbeat data.

4. The system according to claim 3, characterized in that The remote data server determines whether a failure occurs in the operation of the local data server based on the status parameter.

5. A method for executing a timed scheduling task, used in the timed scheduling task system according to any one of claims 1 to 4, characterized in that: The steps include: Obtaining the working status of the local data server executing the first scheduled task; Determining whether the working state is in a fault state; When the working state is in a fault state, the remote data server is controlled to pull and trigger a second scheduled task that is consistent with the first scheduled task configuration.

6. The method according to claim 5, characterized in that Also includes: When the local data server is not in the fault state, controlling the local data server to send status parameters to the remote data server at preset intervals, wherein the status parameters include heartbeat data; The remote data server receives the state parameter and determines whether to pull and trigger the second timed scheduling task based on the state parameter.

7. The method according to claim 5, characterized in that Before determining whether the working state is in a fault state, the method further includes: Obtaining the running status of the first scheduled task; Determine whether the running status of the first scheduled task is in the enabled state; When the running state of the first timed scheduling task is in the enabled state, it is determined whether the working state of the local data server is in the fault state.

8. The method according to claim 7, characterized in that Also includes: When the first scheduled task is not started, the remote data server is controlled not to execute the pull operation and trigger operation of the second scheduled task.

9. A device for executing a timed scheduling task, used in the timed scheduling task system according to any one of claims 1 to 4, characterized in that: include: An acquisition module, configured to acquire the working status of the local data server executing the first scheduled task; A judging module, configured to judge whether the working state is in a fault state; A startup module is used to control the remote data server to pull and trigger a second scheduled task that is consistent with the first scheduled task configuration when the working state is in a fault state.

10. A server, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for executing a timed scheduling task as described in any one of claims 5 to 8 by executing the computer instructions.

11. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for executing a timed scheduling task according to any one of claims 5 to 8.

Images