Task scheduling method and device of integrated service platform

Abstract

The application discloses a task scheduling method and device of a comprehensive service platform, which can be applied to the technical field of computer software and has the steps that a task scheduling center receives a scheduling request of a task; the task scheduling center starts a task executor corresponding to the task according to the scheduling request and a pre-established calling relationship; the task executor is used for calling a service interface by using an associated task service node; and the calling relationship is pre-established according to registered tasks and task executors. The application can solve the problems of the existing comprehensive service platform task scheduling, such as occupying additional resources, impacting a cluster mechanism and increasing operation and maintenance costs.

Description

Technical Field

[0001] This invention relates to the field of computer software technology, and in particular to a task scheduling method and apparatus for an integrated service platform. Background Technology

[0002] This section is intended to provide background or context for the embodiments of the invention set forth in the claims. The description herein is not an admission that it is prior art simply because it is included in this section.

[0003] The integrated service platform is a cluster system that adopts a microservice framework. Each application has its own scheduled tasks, and within the same service cluster, only one service node can call the same task.

[0004] In existing technologies, integrated service platforms use separate service nodes outside the cluster to perform application task scheduling, which leads to application services consuming additional resources and impacting the cluster mechanism, increasing operation and maintenance costs. However, if all application tasks are deployed centrally, the service code for tasks will be separated from the business service code, thereby increasing development difficulty and later operation and maintenance costs.

[0005] There is currently no effective solution to the above problems. Summary of the Invention

[0006] This invention provides a task scheduling method for an integrated service platform to address the problems of existing integrated service platforms consuming additional resources, impacting cluster mechanisms, and increasing operational costs. The method includes:

[0007] The task scheduling center receives task scheduling requests;

[0008] The task scheduling center initiates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor is used to call the service interface using the associated task service node. The calling relationship is pre-established based on the registered task and task executor.

[0009] Furthermore, the task scheduling method of the integrated service platform also includes:

[0010] After the task scheduling center activates the task executor corresponding to the task, it sends task execution status information to the console.

[0011] Furthermore, the task scheduling method of the integrated service platform also includes:

[0012] After the task scheduling center starts the task executor corresponding to the task, it sends task log information to the console.

[0013] Furthermore, the calling relationship is pre-established as follows:

[0014] The task scheduling center receives task registration requests and executor registration requests sent from the console;

[0015] The task scheduling center registers the task according to the task registration request;

[0016] The task scheduling center registers the task executor according to the executor registration request;

[0017] The task scheduling center establishes a call relationship based on the registered tasks and task executors.

[0018] Furthermore, the task scheduling method of the integrated service platform also includes:

[0019] After establishing the call relationship, the task scheduling center configures the scheduling rule information;

[0020] The task scheduling center initiates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. This includes: the task scheduling center initiates the task executor corresponding to the task based on the scheduling request, the pre-established calling relationship and scheduling rule information.

[0021] Furthermore, the scheduling rule information includes: routing rule information.

[0022] Furthermore, the scheduling rule information also includes: operating mode information and blocking strategy information.

[0023] This invention provides a task scheduling device for an integrated service platform to address the problems of existing integrated service platforms consuming additional resources, impacting cluster mechanisms, and increasing operational costs during task scheduling. The device includes:

[0024] The scheduling request receiving module is used to receive scheduling requests for tasks.

[0025] The executor initiation module is used to initiate the task executor corresponding to the task according to the scheduling request and the pre-established calling relationship. The task executor is used to call the service interface using the associated task service node. The calling relationship is pre-established based on the registered task and task executor.

[0026] Furthermore, the task scheduling device of the integrated service platform also includes:

[0027] The status information sending module is used to send task execution status information to the console after activating the task executor corresponding to the task.

[0028] Furthermore, the task scheduling device of the integrated service platform also includes:

[0029] The log information sending module is used by the task scheduling center to send task log information to the console after activating the task executor corresponding to the task.

[0030] Furthermore, the calling relationship is pre-established as follows:

[0031] The task scheduling center receives task registration requests and executor registration requests sent from the console;

[0032] The task scheduling center registers the task according to the task registration request;

[0033] The task scheduling center registers the task executor according to the executor registration request;

[0034] The task scheduling center establishes a call relationship based on the registered tasks and task executors.

[0035] Furthermore, the task scheduling device of the integrated service platform also includes:

[0036] The rule information configuration module is used by the task scheduling center to configure scheduling rule information after the call relationship is established;

[0037] The executor initiation module is further used for: the task scheduling center to initiate the task executor corresponding to the task based on the scheduling request, the pre-established calling relationship and scheduling rule information.

[0038] Furthermore, the scheduling rule information includes: routing rule information.

[0039] Furthermore, the scheduling rule information also includes: operating mode information and blocking strategy information.

[0040] This invention also provides a computer device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the task scheduling method of the aforementioned integrated service platform.

[0041] This invention also provides a computer-readable storage medium storing a computer program that executes the task scheduling method of the integrated service platform described above.

[0042] The task scheduling method, apparatus, computer equipment, and computer-readable storage medium of the integrated service platform provided in this embodiment of the invention receive task scheduling requests through a task scheduling center. The task scheduling center, based on the scheduling request and a pre-established calling relationship, activates the task executor corresponding to the task. The task executor uses an associated task service node to call a service interface. The calling relationship is pre-established based on the registered tasks and task executors. Compared to existing technologies that use separate service nodes outside the cluster to complete application task scheduling or centrally deploy all application tasks, this embodiment of the invention pre-establishes a calling relationship based on the registered tasks and task executors. Upon receiving a task scheduling request, it activates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor then uses the associated task service node to call the service interface, thereby realizing task scheduling of the integrated service platform. This eliminates the need for separate service nodes, reducing the impact on the original cluster mechanism and operational costs. Directly calling existing service interfaces decouples scheduling and services, avoiding the separation of two sets of code. Attached Figure Description

[0043] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort. In the drawings:

[0044] Figure 1 This is a flowchart of a task scheduling method for an integrated service platform provided in an embodiment of the present invention;

[0045] Figure 2 This is a flowchart of an optional integrated service platform task scheduling method provided in an embodiment of the present invention;

[0046] Figure 3 This is a flowchart of an optional integrated service platform task scheduling method provided in an embodiment of the present invention;

[0047] Figure 4 This is a flowchart of the method for pre-establishing call relationships provided in this embodiment of the invention;

[0048] Figure 5 This is a schematic diagram of a task scheduling device for an integrated service platform provided in an embodiment of the present invention;

[0049] Figure 6 This is a schematic diagram of a task scheduling device for an optional integrated service platform provided in an embodiment of the present invention;

[0050] Figure 7 This is a schematic diagram of a task scheduling device for an optional integrated service platform provided in an embodiment of the present invention;

[0051] Figure 8 This is a schematic diagram of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0052] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be further described in detail below with reference to the accompanying drawings. Here, the illustrative embodiments of the present invention and their descriptions are used to explain the present invention, but are not intended to limit the present invention.

[0053] To address the issues of existing integrated service platforms consuming additional resources, impacting cluster mechanisms, and increasing operational costs through task scheduling, this invention provides a task scheduling method for integrated service platforms. Figure 1 This is a flowchart of a task scheduling method for an integrated service platform provided in an embodiment of the present invention, such as... Figure 1 As shown, it includes the following steps:

[0054] Step 101: The task scheduling center receives the task scheduling request;

[0055] Step 102: The task scheduling center initiates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor is used to call the service interface using the associated task service node. The calling relationship is pre-established based on the registered task and task executor.

[0056] Depend on Figure 1 As shown, in this embodiment of the invention, a task scheduling center receives task scheduling requests. Based on the scheduling request and a pre-established calling relationship, the task scheduling center activates the task executor corresponding to the task. The task executor uses an associated task service node to call a service interface. The calling relationship is pre-established based on the registered tasks and task executors. Compared to existing technologies that use separate service nodes outside the cluster to complete application task scheduling or centrally deploy all application tasks, this embodiment of the invention pre-establishes a calling relationship based on the registered tasks and task executors. Upon receiving a task scheduling request, it activates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor then uses the associated task service node to call the service interface, thereby realizing task scheduling of the integrated service platform. This eliminates the need for separate service nodes, reducing the impact on the original cluster mechanism and operational costs. Directly calling existing service interfaces decouples scheduling and services, avoiding the separation of two sets of code.

[0057] In this embodiment, the task scheduling center receives a task scheduling request; based on the scheduling request and a pre-established calling relationship, the task scheduling center initiates the task executor corresponding to the task, the task executor is used to call the service interface using the associated task service node, and the calling relationship is pre-established based on the registered task and task executor.

[0058] In this embodiment, as Figure 2 As shown, the task scheduling method of the integrated service platform further includes:

[0059] Step 103: After the task scheduling center starts the task executor corresponding to the task, it sends the task execution status information to the console.

[0060] It should be noted that the task execution status information is the status after the task executor starts. The task execution status information in the executor includes name information, sorting information, registration method information, and scheduling address information, etc.

[0061] In this embodiment, as Figure 3 As shown, the task scheduling method of the integrated service platform further includes:

[0062] Step 104: After the task scheduling center starts the task executor corresponding to the task, it sends task log information to the console.

[0063] It should be noted that the task log information includes task ID information, scheduling time information, scheduling result information, scheduling remarks information, execution time information, execution result information, execution remarks information, and execution log information. The completion status of each scheduling can be queried through the task log information.

[0064] In this embodiment, as Figure 4 As shown, the calling relationship is pre-established in the following manner:

[0065] Step 401: The task scheduling center receives the task registration request and executor registration request sent from the console;

[0066] Step 402: The task scheduling center registers the task according to the task registration request;

[0067] Step 403: The task scheduling center registers the task executor according to the executor registration request;

[0068] Step 404: The task scheduling center establishes a call relationship based on the registered tasks and task executors.

[0069] In practice, when registering a task, an executor is selected. When the task application starts, it is automatically registered to the corresponding executor based on the service parameters. The two are associated through the executor name.

[0070] In this embodiment, the task scheduling method of the integrated service platform further includes: after establishing the calling relationship, the task scheduling center configures scheduling rule information;

[0071] The task scheduling center initiates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. This includes: the task scheduling center initiates the task executor corresponding to the task based on the scheduling request, the pre-established calling relationship and scheduling rule information.

[0072] In this embodiment, the scheduling rule information includes: routing rule information.

[0073] In practice, the routing rule information includes: first service, last service, round-robin information, random information, consistent hash information, least frequently used information, longest recently used information, failover information, and busy failover information. In a cluster deployment, each task corresponds to multiple services; the first service and last service refer to the first and last services within the task.

[0074] In this embodiment, the scheduling rule information further includes: operating mode information and blocking strategy information.

[0075] In specific implementation, the running mode information includes: JAVA BEAN running mode, and the blocking strategy information includes: single-machine serial information, discarding subsequent scheduling information, and overwriting previous scheduling information.

[0076] The following is an example illustrating the specific application of the task scheduling scheme of the integrated service platform of the present invention.

[0077] The task scheduling for the integrated service platform should be performed according to the following process:

[0078] 1. Developers can implement the application's task entry point and business flow functions after task scheduling without having to worry about the task initiation method.

[0079] 2. Implementation and maintenance: Register the task executor and the task through the console, establish the calling relationship between the task and the executor, and configure routing rules, running mode and blocking policy;

[0080] 3. When deploying an application, the cluster service automatically associates with the task executor in the task scheduling center using built-in tools;

[0081] 4. The task scheduling center initiates the task executor through tasks, configurations, and scheduling rules, and then uses the executor to call the flow of task jobs;

[0082] 5. Administrators can monitor the current status of tasks and view task history logs in real time through the console.

[0083] In summary, this embodiment of the invention receives task scheduling requests through a task scheduling center. Based on the scheduling request and a pre-established calling relationship, the task scheduling center activates the task executor corresponding to the task. The task executor uses an associated task service node to call a service interface. The calling relationship is pre-established based on the registered tasks and task executors. Compared to existing technologies that use separate service nodes outside the cluster to complete application task scheduling or centrally deploy all application tasks, this embodiment of the invention pre-establishes a calling relationship based on the registered tasks and task executors. Upon receiving a task scheduling request, it activates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor then uses the associated task service node to call the service interface, thereby achieving task scheduling for the integrated service platform. This eliminates the need for separate service nodes, reducing the impact on the original cluster mechanism and operational costs. Directly calling existing service interfaces decouples scheduling and services, avoiding the separation of two sets of code.

[0084] Based on the same inventive concept, this invention also provides a task scheduling device for an integrated service platform, as described in the following embodiments. Since the principle by which this device solves the problem is similar to the task scheduling method of the integrated service platform, the implementation of this device can refer to the implementation of the task scheduling method of the integrated service platform; repeated details will not be elaborated further.

[0085] Figure 5 This is a schematic diagram of a task scheduling device for an integrated service platform provided in an embodiment of the present invention, such as... Figure 5 As shown, the task scheduling device of the integrated service platform provided in this embodiment of the invention may include:

[0086] The scheduling request receiving module 501 is used to receive scheduling requests for tasks;

[0087] The executor initiation module 502 is used to initiate the task executor corresponding to the task according to the scheduling request and the pre-established calling relationship. The task executor is used to call the service interface using the associated task service node. The calling relationship is pre-established according to the registered task and task executor.

[0088] In one embodiment, such as Figure 6 As shown, the task scheduling device of the integrated service platform provided in this embodiment of the invention may further include:

[0089] The status information sending module 503 is used to send task execution status information to the console after activating the task executor corresponding to the task.

[0090] In one embodiment, such as Figure 7 As shown, the task scheduling device of the integrated service platform provided in this embodiment of the invention may further include:

[0091] The log information sending module 504 is used to send task log information to the console after the task scheduling center starts the task executor corresponding to the task.

[0092] In one embodiment, the calling relationship is pre-established as follows:

[0093] The task scheduling center receives task registration requests and executor registration requests sent from the console;

[0094] The task scheduling center registers the task according to the task registration request;

[0095] The task scheduling center registers the task executor according to the executor registration request;

[0096] The task scheduling center establishes a call relationship based on the registered tasks and task executors.

[0097] In one embodiment, the task scheduling device of the integrated service platform further includes:

[0098] The rule information configuration module is used by the task scheduling center to configure scheduling rule information after the call relationship is established;

[0099] The executor initiation module is further used for: the task scheduling center to initiate the task executor corresponding to the task based on the scheduling request, the pre-established calling relationship and scheduling rule information.

[0100] In one embodiment, the scheduling rule information includes: routing rule information.

[0101] In one embodiment, the scheduling rule information further includes: running mode information and blocking policy information.

[0102] It should be noted that the scheduling request receiving module 501, executor initiation module 502, status information sending module 503, and log information sending module 504 mentioned above correspond to steps 101 to 104 in the method embodiment. The examples and application scenarios implemented by the above modules and their corresponding steps are the same, but they are not limited to the content disclosed in the above method embodiment. It should be noted that the above modules, as part of the device, can be executed in a computer system such as a set of computer-executable instructions.

[0103] In summary, this embodiment of the invention receives task scheduling requests through a task scheduling center. Based on the scheduling request and a pre-established calling relationship, the task scheduling center activates the task executor corresponding to the task. The task executor uses an associated task service node to call a service interface. The calling relationship is pre-established based on the registered tasks and task executors. Compared to existing technologies that use separate service nodes outside the cluster to complete application task scheduling or centrally deploy all application tasks, this embodiment of the invention pre-establishes a calling relationship based on the registered tasks and task executors. Upon receiving a task scheduling request, it activates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor then uses the associated task service node to call the service interface, thereby achieving task scheduling for the integrated service platform. This eliminates the need for separate service nodes, reducing the impact on the original cluster mechanism and operational costs. Directly calling existing service interfaces decouples scheduling and services, avoiding the separation of two sets of code.

[0104] Based on the same inventive concept, this invention also provides an embodiment of an electronic device for implementing all or part of the task scheduling method of the aforementioned integrated service platform. This electronic device specifically includes the following:

[0105] The device comprises a processor, memory, a communications interface, and a bus; wherein the processor, memory, and communications interface communicate with each other via the bus; the communications interface is used to realize information transmission between related devices; the electronic device can be a desktop computer, tablet computer, or mobile terminal, etc., and this embodiment is not limited to these. In this embodiment, the electronic device can be implemented with reference to the embodiments for implementing the task scheduling method of the above-mentioned integrated service platform and the embodiments for implementing the task scheduling device of the above-mentioned integrated service platform, the contents of which are incorporated herein, and repeated details will not be described again.

[0106] Figure 8 This is a schematic diagram of the system composition structure of an electronic device provided in an embodiment of the present invention. Figure 8 As shown, the electronic device 80 may include a processor 801 and a memory 802; the memory 802 is coupled to the processor 801. It is worth noting that... Figure 8 This is an example; other types of structures can also be used to supplement or replace this structure to achieve telecommunications functions or other functions.

[0107] In one embodiment, the functionality of the task scheduling method of the integrated service platform can be integrated into the processor 801. The processor 801 can be configured to perform the following control: the task scheduling center receives a task scheduling request; the task scheduling center, based on the scheduling request and a pre-established calling relationship, initiates the task executor corresponding to the task, the task executor being used to call the service interface using the associated task service node, the calling relationship being pre-established based on the registered task and task executor.

[0108] As can be seen from the above, the electronic device provided in the embodiments of the present invention receives the scheduling request of the task through the task scheduling center; the task scheduling center activates the task executor corresponding to the task according to the scheduling request and the pre-established calling relationship, the task executor is used to call the service interface using the associated task service node, and the calling relationship is pre-established according to the registered task and the task executor.

[0109] The electronic device provided in this embodiment of the invention can establish a pre-established calling relationship based on the registered task and task executor. After receiving the scheduling request of the task, it can start the task executor corresponding to the task according to the scheduling request and the pre-established calling relationship. Then, the task executor will use the associated task service node to call the service interface, thereby realizing the task scheduling of the integrated service platform. There is no need to deploy service nodes separately, which reduces the impact on the original cluster mechanism and the operation and maintenance costs. Directly calling the existing service interface realizes the decoupling of scheduling and service, avoiding the separation of two sets of code.

[0110] In another embodiment, the task scheduling device of the integrated service platform can be configured separately from the processor 801. For example, the task scheduling device of the integrated service platform can be configured as a chip connected to the processor 801, and the function of the task scheduling method of the integrated service platform can be realized through the control of the processor.

[0111] like Figure 8 As shown, the electronic device 80 may further include: a communication module 803, an input unit 804, an audio processing unit 805, a display 806, and a power supply 807. It is worth noting that the electronic device 80 does not necessarily need to include these components. Figure 8 All components shown; in addition, the electronic device 80 may also include Figure 8 For components not shown, please refer to existing technology.

[0112] like Figure 8 As shown, processor 801, sometimes also referred to as controller or operation control, may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of electronic device 80.

[0113] The memory 802 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It may store the aforementioned failure-related information, and also store a program for executing that information. The processor 801 may execute the program stored in the memory 802 to perform information storage or processing, etc.

[0114] Input unit 804 provides input to processor 801. Input unit 804 may be, for example, a keypad or touch input device. Power supply 807 provides power to electronic device 80. Display 806 displays images and text. Display may be, for example, an LCD display, but is not limited to this.

[0115] The memory 802 can be a solid-state memory, such as a read-only memory (ROM), random access memory (RAM), SIM card, etc. It can also be a memory that retains information even when power is off, can be selectively erased, and contains more data; examples of this type of memory are sometimes referred to as EPROMs. The memory 802 can also be some other type of device. The memory 802 includes a buffer memory 8021 (sometimes called a buffer). The memory 802 may include an application / function storage unit 8022 for storing application programs and function programs or processes for executing the operation of the electronic device 80 via the processor 801.

[0116] The memory 802 may also include a data storage unit 8023 for storing data, such as contacts, digital data, pictures, sounds, and / or any other data used by the electronic device. The driver storage unit 8024 of the memory 802 may include various drivers for the electronic device for communication functions and / or for performing other functions of the electronic device (such as messaging applications, address book applications, etc.).

[0117] The communication module 803 is a transmitter / receiver that sends and receives signals via the antenna 808. The communication module (transmitter / receiver) 803 is coupled to the processor 801 to provide input signals and receive output signals, which is the same as in a conventional mobile communication terminal.

[0118] Based on different communication technologies, multiple communication modules 803 can be configured in the same electronic device, such as cellular network modules, Bluetooth modules, and / or wireless LAN modules. The communication module (transmitter / receiver) 803 is also coupled to a speaker 809 and a microphone 810 via an audio processing unit 805 to provide audio output via the speaker 809 and receive audio input from the microphone 810, thereby realizing typical telecommunications functions. The audio processing unit 805 may include any suitable buffer, decoder, amplifier, etc. Additionally, the audio processing unit 805 is also coupled to a processor 801, enabling on-device recording via the microphone 810 and on-device playback of stored audio via the speaker 809.

[0119] In embodiments of the present invention, a computer-readable storage medium is also provided for implementing all steps of the task scheduling method of the integrated service platform in the above embodiments. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements all steps of the task scheduling method of the integrated service platform in the above embodiments. For example, when the processor executes the computer program, it implements the following steps: the task scheduling center receives a task scheduling request; the task scheduling center, according to the scheduling request and a pre-established calling relationship, initiates the task executor corresponding to the task; the task executor is used to call the service interface using the associated task service node; the calling relationship is pre-established based on the registered task and the task executor.

[0120] As can be seen from the above, the computer-readable storage medium provided in the embodiments of the present invention receives the scheduling request of a task through a task scheduling center; the task scheduling center initiates the task executor corresponding to the task according to the scheduling request and the pre-established calling relationship, the task executor is used to call the service interface using the associated task service node, and the calling relationship is pre-established according to the registered task and task executor.

[0121] The computer-readable storage medium provided in this embodiment of the invention enables the pre-establishment of a calling relationship between the registered task and the task executor. Upon receiving a task scheduling request, the task executor corresponding to the task is invoked according to the scheduling request and the pre-established calling relationship. The task executor then uses the associated task service node to call the service interface, thereby realizing task scheduling of the integrated service platform. This eliminates the need to deploy separate service nodes, thus reducing the impact on the original cluster mechanism and the operation and maintenance costs. Directly calling the existing service interface achieves the decoupling of scheduling and service, avoiding the separation of two sets of code.

[0122] While this invention provides the method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-inventive labor. The order of steps listed in the embodiments is merely one possible execution order among many and does not represent the only possible execution order. In actual device or client product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment).

[0123] Those skilled in the art will understand that the embodiments of this specification can be provided as methods, apparatus (systems), or computer program products. Therefore, the embodiments of this specification can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0124] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0125] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0126] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0127] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, the system embodiments are relatively simple in description because they are fundamentally similar to the method embodiments; relevant parts can be referred to the descriptions in the method embodiments. In this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "upper," "lower," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore should not be construed as limiting the invention. Unless otherwise expressly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; mechanical connections or electrical connections; direct connections or indirect connections through an intermediate medium; and internal connections between two components. Those skilled in the art can understand the specific meaning of these terms in this invention according to the specific circumstances. It should be noted that, without conflict, the embodiments and features in the embodiments of this invention can be combined with each other. This invention is not limited to any single aspect, nor to any single embodiment, nor to any combination and / or substitution of these aspects and / or embodiments. Each aspect and / or embodiment of this invention can be used alone, or in combination with one or more other aspects and / or other embodiments.

[0128] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention, and they should all be covered within the scope of the claims and specification of the present invention.

Claims

1. A task scheduling method for an integrated service platform, characterized in that, include: The task scheduling center receives task scheduling requests; The task scheduling center initiates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship. The task executor is used to call the service interface using the associated task service node to achieve decoupling of scheduling and service. The calling relationship is pre-established based on the registered task and task executor. The cluster service automatically associates with the task executor of the task scheduling center through built-in tools during application deployment; After establishing the call relationship, the task scheduling center configures the scheduling rule information; The task scheduling center initiates the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship, including: the task scheduling center initiates the task executor corresponding to the task based on the scheduling request, the pre-established calling relationship and scheduling rule information; The scheduling rule information includes: routing rule information, operating mode information, and blocking policy information; the operating mode information includes: JAVA BEAN operating mode; the blocking policy information includes: single-machine serial information, discarding subsequent scheduling information, and overwriting previous scheduling information; The routing rule information includes: first service, last service, round-robin information, random information, consistent hash information, least frequently used information, most recently used information, failover information, and busy failover information. In the cluster deployment, each task has multiple corresponding services. The first service and the last service refer to the first and last services in the task. The calling relationship is established in advance as follows: The task scheduling center receives the task registration request and the executor registration request sent by the console; the task scheduling center registers the task according to the task registration request; the task scheduling center registers the task executor according to the executor registration request; the task scheduling center establishes the calling relationship based on the registered task and task executor. When registering a task, an executor is selected. When the task application starts, it is automatically registered to the corresponding executor based on the service parameters. The two are associated through the executor name.

2. The task scheduling method of the integrated service platform as described in claim 1, characterized in that, Also includes: After the task scheduling center activates the task executor corresponding to the task, it sends task execution status information to the console.

3. The task scheduling method of the integrated service platform as described in claim 1, characterized in that, Also includes: After the task scheduling center starts the task executor corresponding to the task, it sends task log information to the console.

4. A task scheduling device for an integrated service platform, characterized in that, include: The scheduling request receiving module is used to receive scheduling requests for tasks. The executor initiation module is used to initiate the task executor corresponding to the task according to the scheduling request and the pre-established calling relationship. The task executor is used to call the service interface using the associated task service node to achieve decoupling of scheduling and service. The calling relationship is pre-established according to the registered task and task executor. Also includes: The rule information configuration module is used by the task scheduling center to configure scheduling rule information after the call relationship is established; The executor initiation module is further used for: the task scheduling center to initiate the task executor corresponding to the task based on the scheduling request and the pre-established calling relationship and scheduling rule information; The scheduling rule information includes: routing rule information; The scheduling rule information also includes: operating mode information and blocking strategy information; The routing rule information includes: first service, last service, round-robin information, random information, consistent hash information, least frequently used information, most recently used information, failover information, and busy failover information. In the cluster deployment, each task has multiple corresponding services. The first service and the last service refer to the first and last services in the task. The calling relationship is established in advance as follows: The task scheduling center receives the task registration request and the executor registration request sent by the console; the task scheduling center registers the task according to the task registration request; the task scheduling center registers the task executor according to the executor registration request; the task scheduling center establishes the calling relationship based on the registered task and task executor. When registering a task, an executor is selected. When the task application starts, it is automatically registered to the corresponding executor based on the service parameters. The two are associated through the executor name.

5. The task scheduling device of the integrated service platform as described in claim 4, characterized in that, Also includes: The status information sending module is used to send task execution status information to the console after activating the task executor corresponding to the task.

6. The task scheduling device of the integrated service platform as described in claim 4, characterized in that, Also includes: The log information sending module is used by the task scheduling center to send task log information to the console after activating the task executor corresponding to the task.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the task scheduling method of the integrated service platform according to any one of claims 1 to 3.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that executes the task scheduling method of the integrated service platform according to any one of claims 1 to 3.

Images