CN110673936A - Breakpoint continuous operation method and device for arranging service, storage medium and electronic equipment - Google Patents
Breakpoint continuous operation method and device for arranging service, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN110673936A CN110673936A CN201910879434.6A CN201910879434A CN110673936A CN 110673936 A CN110673936 A CN 110673936A CN 201910879434 A CN201910879434 A CN 201910879434A CN 110673936 A CN110673936 A CN 110673936A
- Authority
- CN
- China
- Prior art keywords
- execution
- information
- node
- service
- executed
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a breakpoint continued operation method, a breakpoint continued operation device, a storage medium and electronic equipment for arranging services, which belong to the technical field of service node management, and comprise the following steps: when the target service node fails to execute, storing the executed information of all the service nodes in a preset position; generating node continuous execution information, and inputting the target service node for execution; when the target service node can continue to execute, acquiring executed information of all service nodes from the preset position, recovering the executed information to the local, and updating the executed information; storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information; and executing the unexecuted queue to complete breakpoint continuous operation when the target service node fails to execute. When the service node is broken, the executed information is updated after the node continuously conducts the debugging of the break point based on the pre-storage of the executed information at the break point, and the break point continuous operation efficiency and the break point continuous operation success rate are guaranteed.
Description
Technical Field
The present application relates to the technical field of service node management, and in particular, to a method, an apparatus, a storage medium, and an electronic device for arranging a breakpoint continuation of a service.
Background
The service arrangement has the functions of determining the execution sequence of the atomic service, judging the execution condition of the atomic service and ensuring that the integrated new service can normally work according to the requirements of a business designer.
The editing tool is very popular at present, but the editing is only responsible for organizing the service functions to be executed according to a certain sequence, and if the execution of a certain node fails in the process, the executed node needs to be rolled back or breakpoint resumed. In the prior art, if the execution process of the orchestration service is interrupted, that is, when a breakpoint occurs, the executed service needs to be released, then the breakpoint is adjusted, and then the orchestration service is re-executed, so that the breakpoint continued operation efficiency is low.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present application and therefore may include information that does not constitute prior art known to a person of ordinary skill in the art.
Disclosure of Invention
The present application aims to provide a breakpoint continuous operation scheme for arranging a service, so that when a service node is at a breakpoint, at least to a certain extent, by pre-storing executed information at the breakpoint, the executed information is updated after debugging the breakpoint of the node continuous operation information is generated, and breakpoint continuous operation efficiency and success rate are ensured.
According to an aspect of the present application, there is provided a breakpoint resuming method for orchestrating a service, including:
when the execution failure of a target service node of a target arrangement service is monitored, storing the executed information of all service nodes of the target arrangement service in a preset position;
generating node continuous operation execution information based on the executed information, and inputting the target service node for execution;
when the target service node is monitored to be capable of continuously executing, acquiring executed information of all the service nodes from the preset position to be recovered to the local, and updating and recovering the executed information of all the service nodes in the local based on the executed information of the node when the target service node is capable of continuously executing;
storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information;
and executing the unexecuted queue to complete breakpoint continuous operation when the target service node fails to execute.
In an exemplary embodiment of the present application, the storing the executed information of all service nodes of the target orchestration service in a predetermined location includes:
serializing the executed information of all service nodes of the target arrangement service to obtain serialized executed information;
saving the serialized executed information in a predetermined location.
In an exemplary embodiment of the present application, the acquiring executed information of all service nodes from the predetermined location and restoring locally includes:
acquiring serialization executed information of all the service nodes from the preset position;
deserializing the serialized executed information to obtain executed information of all service nodes;
and storing the executed information of all the service nodes to the local.
In an exemplary embodiment of the present application, after the executing the non-execution queue to complete the breakpoint continuation when the target service node fails to execute, the method further includes:
and when the unexecuted queue is executed and the target service node is successfully executed, storing the target service node into an execution success queue, and finishing breakpoint continuous operation when the target service node is failed to be executed.
In an exemplary embodiment of the present application, the generating a node continuation execution information based on the executed information, and inputting the target service node for execution includes:
acquiring partial executed information excluding the executed information of the target service node in the executed information;
acquiring a node execution parameter of the target service node;
and inputting the part of executed information and the node execution parameters into a pre-trained machine learning model to obtain node continuous operation execution information, and inputting the node continuous operation execution information into the target service node for execution.
In an exemplary embodiment of the present application, after the storing, when it is monitored that the execution of the target service node of the target orchestration service fails, the executed information of all service nodes of the target orchestration service in a predetermined location, the method further includes:
acquiring execution information when the execution of the target service node fails;
and modifying the execution parameters of the target service node according to the execution information when the execution fails.
In an exemplary embodiment of the present application, modifying the execution parameter of the target service node according to the execution information when the execution fails includes:
acquiring a service node parameter constraint table, wherein the service node parameter constraint table comprises node information, execution parameter information when execution fails and execution parameter resetting parameters;
searching a target execution parameter resetting parameter from the service node parameter constraint table according to the execution information when the execution fails;
and resetting the execution parameters of the target service node according to the target execution parameter resetting parameters.
According to an aspect of the present application, there is provided an apparatus for scheduling a breakpoint continuation of a service, comprising:
the storage module is used for storing the executed information of all service nodes of the target arrangement service in a preset position when the execution failure of the target service node of the target arrangement service is monitored;
the test module is used for generating node continuous operation execution information based on the executed information and inputting the target service node for execution;
a monitoring module, configured to, when it is monitored that the target service node can continue to execute, obtain executed information of all the service nodes from the predetermined location and restore the executed information to the local, and update the executed information of all the service nodes restored to the local based on the node continued execution information when the target service node can continue to execute;
the pre-execution module is used for storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information;
and the execution module is used for executing the unexecuted queue so as to complete breakpoint continuous operation when the target service node fails to execute.
According to an aspect of the present application, there is provided a computer-readable storage medium having stored thereon a breakpoint continuation program of an orchestration service, wherein the breakpoint continuation program of the orchestration service, when executed by a processor, implements the method of any one of the above.
According to an aspect of the present application, there is provided an electronic device, comprising:
a processor; and
the memory is used for storing a breakpoint continuous program of the arrangement service of the processor; wherein the processor is configured to perform any of the methods described above via execution of a breakpoint resume of the orchestration service.
Firstly, when the execution failure of a target service node of a target arrangement service is monitored, storing the executed information of all service nodes of the target arrangement service in a preset position; therefore, the executed information of all the service nodes can be stored in time and can be conveniently acquired. Then, based on the executed information, generating node continuous operation execution information, and inputting the target service node for execution; node continuation execution information for verifying the target service node may be generated by executing the verification of the target service node. Then, in the execution process, when it is monitored that the target service node can be continuously executed, indicating that node continuous execution information is matched with the target service node, acquiring executed information of all service nodes from the preset position to restore the executed information to the local, and updating and restoring the executed information of all service nodes in the local based on the node continuous execution information when the target service node can be continuously executed; this makes it possible to obtain execution information for executing the next node. Further, storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information; all nodes can be clearly shown and accurately executed through the execution queue. And finally, executing the unexecuted queue to complete breakpoint continuous operation when the target service node fails to execute. Therefore, when the service node is broken, the executed information is updated after the node continuous operation execution information debugging broken point is generated through the pre-storage of the executed information at the broken point, and the broken point continuous operation efficiency and the success rate are ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. It is obvious that the drawings in the following description are only some embodiments of the application, and that for a person skilled in the art, other drawings can be derived from them without inventive effort.
Fig. 1 schematically shows a flow chart of a breakpoint resumption method for orchestrating a service.
Fig. 2 schematically shows an exemplary application scenario of a breakpoint continuation method for orchestrating services.
Fig. 3 schematically shows a flow chart of a method for the generating node to continue execution of the execution information.
Fig. 4 schematically shows a block diagram of a breakpoint resume apparatus for orchestrating a service.
Fig. 5 schematically shows an exemplary block diagram of an electronic device for implementing the breakpoint resume method of orchestration service described above.
Fig. 6 schematically illustrates a computer-readable storage medium for implementing the breakpoint resume method for orchestrating services described above.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the application. One skilled in the relevant art will recognize, however, that the subject matter of the present application can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and so forth. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present application.
Furthermore, the drawings are merely schematic illustrations of the present application and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
In this exemplary embodiment, a breakpoint continuous operation method of an orchestration service is first provided, where the breakpoint continuous operation method of the orchestration service may be executed on a server, or may be executed on a server cluster or a cloud server, and the like. Referring to fig. 1, the breakpoint resuming method for orchestrating service may include the following steps:
step S110, when the execution failure of the target service node of the target arrangement service is monitored, the executed information of all the service nodes of the target arrangement service is stored in a preset position;
step S120, generating node continuous operation execution information based on the executed information, and inputting the target service node for execution;
step S130, when it is monitored that the target service node can continue to execute, acquiring executed information of all the service nodes from the predetermined location to restore the executed information to the local, and updating and restoring the executed information of all the service nodes in the local based on the node continued execution information that the target service node can continue to execute;
step S140, storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information;
step S150, executing the unexecuted queue to complete the breakpoint operation when the target service node fails to execute.
In the breakpoint continuous operation method for arranging the service, firstly, when the execution failure of a target service node of the target arrangement service is monitored, the executed information of all service nodes of the target arrangement service is stored in a preset position; therefore, the executed information of all the service nodes can be stored in time and can be conveniently acquired. Then, based on the executed information, generating node continuous operation execution information, and inputting the target service node for execution; node continuation execution information for verifying the target service node may be generated by executing the verification of the target service node. Then, in the execution process, when it is monitored that the target service node can be continuously executed, indicating that node continuous execution information is matched with the target service node, acquiring executed information of all service nodes from the preset position to restore the executed information to the local, and updating and restoring the executed information of all service nodes in the local based on the node continuous execution information when the target service node can be continuously executed; this makes it possible to obtain execution information for executing the next node. Further, storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information; all nodes can be clearly shown and accurately executed through the execution queue. And finally, executing the unexecuted queue to complete breakpoint continuous operation when the target service node fails to execute. Therefore, when the service node is broken, the executed information is updated after the node continuous operation execution information debugging broken point is generated through the pre-storage of the executed information at the broken point, and the broken point continuous operation efficiency and the success rate are ensured.
Hereinafter, the steps of the breakpoint continuous operation method for arranging the service in the exemplary embodiment will be explained and explained in detail with reference to the drawings.
In step S110, when it is monitored that the target service node of the target orchestration service fails to execute, the executed information of all service nodes of the target orchestration service is stored in a predetermined location.
In the embodiment of the present example, referring to fig. 2, when monitoring that a target cloud host on a server 202 is initialized and started, a server 201 obtains a target preset startup initialization policy package corresponding to the target cloud host. This may be initialized by the server 201 in subsequent steps based on the initialization policy package. It can be understood that, according to a requirement, the server 202 may also directly obtain a target preset start initialization policy package corresponding to the target cloud host, and perform initialization based on the initialization policy package in subsequent steps. The server 201 and the server 202 may be any devices with processing capability, such as a computer, a microprocessor, etc., and are not limited herein.
The arranging service is executed by a plurality of service nodes according to a preset arranging sequence, when a certain condition that execution fails occurs in the arranging service executing process, namely a breakpoint occurs, the executed information of all service nodes of the target arranging service is stored in a preset storage position such as a database or a cloud end, so that the execution can be resumed on the basis of the stored executed information when the node which fails to execute can be executed again, and the efficiency of continuous operation of the arranging service breakpoint is effectively ensured, namely the efficiency of continuous execution of the arranging service from the breakpoint. The executed information is the information of the entry, exit and execution states of each node.
In an embodiment of this example, the storing the executed information of all service nodes of the target orchestration service in a predetermined location includes:
serializing the executed information of all service nodes of the target arrangement service to obtain serialized executed information;
saving the serialized executed information in a predetermined location.
Serializing executed information of all service nodes of the target orchestration service to obtain serialized executed information, for example, serializing a tree graph of each orchestration call node and entry, exit, execution states (unexecuted, executed successfully, execution failed) and the like of each execution node according to a call sequence and an execution sequence, and then storing the serialized information into a data block DB. Accurate and fast saving of executed information can be achieved.
In step S120, based on the executed information, the generating node continues to execute the information, and inputs the target service node for execution.
In the embodiment of the present example, the node continuation execution information is used to verify the node continuation execution information of the target service node, and the target service node is verified by the execution. The node continuation execution information mainly includes continuation execution information of the target service node from the start of execution to the end of execution, for example, a plurality of standard check execution information corresponding to the target service node that are preset or a plurality of node continuation execution information of the target service node predicted based on the executed information. Therefore, based on the executed information, the node continuous operation execution information is generated and the target service node is input for execution, and the target service node of the breakpoint can be quickly checked. The method for inputting the node continuous execution information into the target service node for execution may be that a plurality of node continuous execution information are sequentially input into the target service node for execution, and it is known that the execution of the node continuous execution information is successful.
In an implementation manner of this example, referring to fig. 3, the generating node continuation execution information based on the executed information and inputting the target service node for execution includes:
step S310, acquiring partial executed information excluding the executed information of the target service node in the executed information;
step S320, obtaining a node execution parameter of the target service node;
step S330, inputting the part of executed information and the node execution parameters into a machine learning model trained in advance to obtain node continuous operation execution information, and inputting the node continuous operation execution information into the target service node for execution.
The executed information of the executed information excluding the execution information of the target service node is the information including the entry of the target service node, and the node execution parameter of the target service node is the execution parameter for executing the entry and the exit, such as an execution function or a control execution sequence. The partial executed information and the node execution parameters can accurately reflect the future execution information of the target node. Furthermore, part of executed information and node execution parameters are input into a machine learning model which is trained in advance, so that at least one possible node can be accurately obtained to continue to execute information, and the information is input into the target service node to execute.
In an embodiment of this example, the training method of the machine learning model is:
collecting a sample set of partial executed information and node execution parameters, wherein each sample in the sample set marks a node in advance and continues to be used as execution information;
respectively inputting the input data of each sample in the sample set into a learning model to obtain the continuous execution information of the node corresponding to each sample;
if the node continuous execution information corresponding to the obtained sample is inconsistent with the node continuous execution information calibrated in advance for the sample after the input data of the sample is input into the learning model, adjusting the coefficient of the learning model until the node continuous execution information is consistent;
and when the input data of all the samples are input into the learning model, the obtained continuous operation execution information of the node corresponding to each sample is consistent with the continuous operation execution information of the node calibrated in advance for each sample, and the training is finished.
The samples of the partial executed information and the node execution parameters are samples of the partial executed information and the acquired node execution parameters of the target service node, which historically correspond to the execution information of the target service node in some executed information. By collecting part of executed information and a node execution parameter sample set as the input of the first learning model, each sample is calibrated by an expert to corresponding nodes to continue executing information as the output of the machine learning model. Then, after the input data of all samples are input into the learning model by adjusting the coefficient, the obtained continuous operation execution information of the node corresponding to each sample is consistent with the continuous operation execution information of the node calibrated in advance for each sample, and the training is finished to obtain the trained machine learning model, so that the training accuracy can be effectively ensured.
In step S130, when it is monitored that the target service node can continue to execute, the executed information of all the service nodes is acquired from the predetermined location and restored locally, and the executed information of all the service nodes restored locally is updated based on the node continued execution information when the target service node can continue to execute.
In this exemplary embodiment, when it is monitored that the target service node can continue to execute, for example, the target service node resumes executing due to a temporary interruption, the executed information of all service nodes can be quickly obtained from the predetermined location for storing the executed information, and be resumed locally. Therefore, the quick recovery of the executed information of the arrangement service can be realized, the second execution of the executed node is not needed to be carried out again, and the efficiency of breakpoint continuous operation is effectively ensured. And updating and recovering the executed information of all the local service nodes based on the node continued execution information of the target service node which can be continuously executed, namely, the node continued execution information of the target service node which can be continuously executed is connected in series with the executed information of all the executed nodes except the executed information of the target service node before interruption to form new executed information of the target service node which is successfully executed, so that the target service node can be directly skipped to enter the next node of the target service node for execution during the continuous execution in the subsequent steps, and the influence of a breakpoint on the service execution process is effectively avoided.
In an implementation manner of this example, the acquiring executed information of all service nodes from the predetermined location and restoring to the local includes:
acquiring serialization executed information of all the service nodes from the preset position;
deserializing the serialized executed information to obtain executed information of all service nodes;
and storing the executed information of all the service nodes to the local.
Acquiring serialization executed information of all service nodes from a preset position, for example, when the problem of a failed node is processed, performing breakpoint continuation again, firstly deserializing the dendrogram for arranging service call and the serialization information of the nodes from the data block DB and storing the deserialized information in a memory before the breakpoint continuation. Therefore, the executed information calling condition can be accurately recovered, and the accuracy in continuous execution is ensured.
In one embodiment, the executed information from all the service nodes comprises:
and the execution parameter information, the execution sequence information and the execution state information of all the service nodes.
In step S140, all the service nodes are stored in the unexecuted queue according to the execution sequence of each service node in the updated executed information.
In the present exemplary embodiment, the non-execution queue is a queue stored by the service node to be ready for execution. When the scheduling service is executed, the execution of the unexecuted queue is directly carried out. Furthermore, an executed queue for storing executed nodes can be further included. All service nodes, namely all service nodes in the arrangement service which stores all executed information when the target service node is interrupted, are stored in the unexecuted queue according to the execution sequence of each service node in the executed information, so that the unexecuted queue can be directly executed in the subsequent steps, control and management are executed by the service nodes, and efficient breakpoint operation is realized.
In step S150, the unexecuted queue is executed to complete the breakpoint operation when the target service node fails to execute.
In the embodiment of the present example, by executing the unexecuted queue, the target orchestration service can start from the root node again, read the information of the node, the executed information is not repeatedly executed, the breakpoint is quickly restored to enter the execution of the next node, and the breakpoint continuation when the target service node fails to execute is completed.
In an implementation manner of this example, after the executing the unexecuted queue to complete the breakpoint continuation when the target service node fails to execute, the method further includes:
and when the unexecuted queue is executed and the target service node is successfully executed, storing the target service node into an execution success queue, and finishing breakpoint continuous operation when the target service node is failed to be executed.
By executing the unexecuted queue, the target arrangement service can be started from the root node again, the information of the node is read, the breakpoint is quickly recovered, the execution state of the node is judged by reading the information of the node, if the node is successfully executed, the node is put into the executed successful queue, and at this moment, the interrupted node is indicated to be successful continuously. Wherein the executed success queue is used for storing the service nodes which have executed successfully.
In an implementation manner of this example, after the storing, when it is detected that the target service node of the target orchestration service fails to execute, the executed information of all service nodes of the target orchestration service in a predetermined location, the method further includes:
acquiring execution information when the execution of the target service node fails;
and modifying the execution parameters of the target service node according to the execution information when the execution fails.
The step of obtaining the execution information when the execution of the target service node fails is to obtain the partial executed information of the target service node, such as the entry, exit, execution state, and the like, in all the executed information. The information can reflect the condition of node parameter setting error in the execution parameter information of the node causing the target service node to fail to execute, namely reflect the setting condition of the execution parameter of the target service node. Furthermore, the execution parameters of the target service node can be accurately modified according to the execution information when the execution fails.
In an implementation manner of this example, modifying the execution parameter of the target service node according to the execution information when the execution fails includes:
acquiring a service node parameter constraint table, wherein the service node parameter constraint table comprises node information, execution parameter information when execution fails and execution parameter resetting parameters;
searching a target execution parameter resetting parameter from the service node parameter constraint table according to the execution information when the execution fails;
and resetting the execution parameters of the target service node according to the target execution parameter resetting parameters.
The service node parameter constraint table is a preset entry, exit and execution state query table, so that the execution parameter information corresponding to each node information when the execution of the entry, exit and execution states fails can be quickly searched, and various reset parameters of the execution parameters of the corresponding target service node can be acquired. Furthermore, the parameters can be reset according to the target execution parameters, the execution parameters of the target service node can be accurately reset, the target node is re-executed, and the breakpoint continuous operation is completed.
The application also provides a breakpoint continuous-making device for arranging the service. Referring to fig. 4, the breakpoint resuming device for orchestration service may include a storage module 410, a testing module 420, a monitoring module 430, a pre-execution module 440, and an execution module 450. Wherein:
the storage module 410 may be configured to, when it is monitored that a target service node of a target orchestration service fails to execute, store executed information of all service nodes of the target orchestration service in a predetermined location;
the test module 420 may be configured to generate node continuation execution information based on the executed information, and input the target service node for execution;
the monitoring module 430 may be configured to, when it is monitored that the target service node can continue to execute, obtain executed information of all the service nodes from the predetermined location to be restored locally, and update the executed information of all the service nodes restored locally based on the node continuation execution information when the target service node can continue to execute;
the pre-execution module 440 may be configured to store all the service nodes in an unexecuted queue according to an execution sequence of each service node in the updated executed information;
the execution module 450 may be configured to execute the unexecuted queue to complete a breakpoint continuation when the target service node fails to execute.
The specific details of each module in the breakpoint continuous operation device of the orchestration service have been described in detail in the breakpoint continuous operation method of the corresponding orchestration service, and therefore are not described herein again.
It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the application. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods herein are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.
In an exemplary embodiment of the present application, there is also provided an electronic device capable of implementing the above method.
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.
An electronic device 500 according to this embodiment of the invention is described below with reference to fig. 5. The electronic device 500 shown in fig. 5 is only an example and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 5, the electronic device 500 is embodied in the form of a general purpose computing device. The components of the electronic device 500 may include, but are not limited to: the at least one processing unit 510, the at least one memory unit 520, and a bus 530 that couples various system components including the memory unit 520 and the processing unit 510.
Wherein the storage unit stores program code that is executable by the processing unit 510 to cause the processing unit 510 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification. For example, the processing unit 510 may execute step S110 as shown in fig. 1: when the execution failure of a target service node of a target arrangement service is monitored, storing the executed information of all service nodes of the target arrangement service in a preset position; s120: generating node continuous operation execution information based on the executed information, and inputting the target service node for execution; step S130: when the target service node is monitored to be capable of continuously executing, acquiring executed information of all the service nodes from the preset position to be recovered to the local, and updating and recovering the executed information of all the service nodes in the local based on the executed information of the node when the target service node is capable of continuously executing; step S140: storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information; step S150: and executing the unexecuted queue to complete breakpoint continuous operation when the target service node fails to execute.
The memory unit 520 may include a readable medium in the form of a volatile memory unit, such as a random access memory unit (RAM)5201 and/or a cache memory unit 5202, and may further include a read only memory unit (ROM) 5203.
The electronic device 500 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a client to interact with the electronic device 500, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 500 to communicate with one or more other computing devices. Such communication may occur via input/output (I/O) interface 550, which may include display unit 540 coupled to input/output (I/O) interface 550. Also, the electronic device 500 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 560. As shown, the network adapter 560 communicates with the other modules of the electronic device 500 over the bus 530. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 500, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiments of the present application.
In an exemplary embodiment of the present application, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.
Referring to fig. 6, a program product 600 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the client computing device, partly on the client device, as a stand-alone software package, partly on the client computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the client computing device over any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., over the internet using an internet service provider).
Furthermore, the above-described figures are merely schematic illustrations of processes involved in methods according to exemplary embodiments of the invention, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
Claims (10)
1. A breakpoint continuous operation method for arranging service is characterized by comprising the following steps:
when the execution failure of a target service node of a target arrangement service is monitored, storing the executed information of all service nodes of the target arrangement service in a preset position;
generating node continuous operation execution information based on the executed information, and inputting the target service node for execution;
when the target service node is monitored to be capable of continuously executing, acquiring executed information of all the service nodes from the preset position to be recovered to the local, and updating and recovering the executed information of all the service nodes in the local based on the executed information of the node when the target service node is capable of continuously executing;
storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information;
and executing the unexecuted queue to complete breakpoint continuous operation when the target service node fails to execute.
2. The method of claim 1, wherein the storing the executed information of all service nodes of the target orchestrated service in a predetermined location comprises:
serializing the executed information of all service nodes of the target arrangement service to obtain serialized executed information;
saving the serialized executed information in a predetermined location.
3. The method of claim 1, wherein said obtaining executed information of all service nodes from the predetermined location and restoring locally comprises:
acquiring serialization executed information of all the service nodes from the preset position;
deserializing the serialized executed information to obtain executed information of all service nodes;
and storing the executed information of all the service nodes to the local.
4. The method of claim 1, wherein after the executing the unexecuted queue to complete a breakpoint continuation when the target service node failed to execute, the method further comprises:
and when the unexecuted queue is executed and the target service node is successfully executed, storing the target service node into an execution success queue, and finishing breakpoint continuous operation when the target service node is failed to be executed.
5. The method of claim 1, wherein generating node continuation execution information based on the executed information and inputting the target service node for execution comprises:
acquiring partial executed information excluding the executed information of the target service node in the executed information;
acquiring a node execution parameter of the target service node;
and inputting the part of executed information and the node execution parameters into a pre-trained machine learning model to obtain node continuous operation execution information, and inputting the node continuous operation execution information into the target service node for execution.
6. The method of claim 1, wherein after the storing the executed information of all service nodes of the target orchestrated service in a predetermined location when the failure of the execution of the target service node of the target orchestrated service is monitored, the method further comprises:
acquiring execution information when the execution of the target service node fails;
and modifying the execution parameters of the target service node according to the execution information when the execution fails.
7. The method of claim 6, wherein modifying the execution parameters of the target service node according to the execution information when the execution fails comprises:
acquiring a service node parameter constraint table, wherein the service node parameter constraint table comprises node information, execution parameter information when execution fails and execution parameter resetting parameters;
searching a target execution parameter resetting parameter from the service node parameter constraint table according to the execution information when the execution fails;
and resetting the execution parameters of the target service node according to the target execution parameter resetting parameters.
8. A breakpoint resumption apparatus for scheduling a service, comprising:
the storage module is used for storing the executed information of all service nodes of the target arrangement service in a preset position when the execution failure of the target service node of the target arrangement service is monitored;
the test module is used for generating node continuous operation execution information based on the executed information and inputting the target service node for execution;
a monitoring module, configured to, when it is monitored that the target service node can continue to execute, obtain executed information of all the service nodes from the predetermined location and restore the executed information to the local, and update the executed information of all the service nodes restored to the local based on the node continued execution information when the target service node can continue to execute;
the pre-execution module is used for storing all the service nodes into an unexecuted queue according to the execution sequence of each service node in the updated executed information;
and the execution module is used for executing the unexecuted queue so as to complete breakpoint continuous operation when the target service node fails to execute.
9. A computer-readable storage medium having stored thereon a breakpoint resume program of an orchestration service, wherein the breakpoint resume program of the orchestration service, when executed by a processor, implements the method of any of claims 1-7.
10. An electronic device, comprising:
a processor; and
the memory is used for storing a breakpoint continuous program of the arrangement service of the processor; wherein the processor is configured to perform the method of any of claims 1-7 via execution of a breakpoint resume of the orchestration service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910879434.6A CN110673936B (en) | 2019-09-18 | 2019-09-18 | Breakpoint continuous operation method and device for arrangement service, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910879434.6A CN110673936B (en) | 2019-09-18 | 2019-09-18 | Breakpoint continuous operation method and device for arrangement service, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110673936A true CN110673936A (en) | 2020-01-10 |
| CN110673936B CN110673936B (en) | 2022-05-17 |
Family
ID=69076700
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910879434.6A Active CN110673936B (en) | 2019-09-18 | 2019-09-18 | Breakpoint continuous operation method and device for arrangement service, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110673936B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110515718A (en) * | 2019-08-30 | 2019-11-29 | 深圳前海微众银行股份有限公司 | Batch tasks breakpoint is continuous to make method, apparatus, equipment and medium |
| CN110825391A (en) * | 2019-10-31 | 2020-02-21 | 北京金山云网络技术有限公司 | Service management method, device, electronic equipment and storage medium |
| CN112527484A (en) * | 2020-12-17 | 2021-03-19 | 平安银行股份有限公司 | Workflow breakpoint continuous running method and device, computer equipment and readable storage medium |
| CN113297081A (en) * | 2021-05-26 | 2021-08-24 | 北京京东振世信息技术有限公司 | Execution method and device of continuous integration assembly line |
| CN116339958A (en) * | 2023-05-30 | 2023-06-27 | 支付宝(杭州)信息技术有限公司 | Task execution method, device and equipment |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040143607A1 (en) * | 2001-06-05 | 2004-07-22 | Silicon Graphics, Inc. | Recovery and relocation of a distributed name service in a cluster filesystem |
| CN102385536A (en) * | 2010-08-27 | 2012-03-21 | 中兴通讯股份有限公司 | Method and system for realization of parallel computing |
| US20130219224A1 (en) * | 2012-02-17 | 2013-08-22 | Nec Corporation | Job continuation management apparatus, job continuation management method and job continuation management program |
| CN106095606A (en) * | 2016-06-12 | 2016-11-09 | 北京三快在线科技有限公司 | A kind of software fault treating method and apparatus of server |
| CN106547613A (en) * | 2016-10-20 | 2017-03-29 | 西北工业大学 | The scheduling of task handling process and fault recovery method |
| US20190243702A1 (en) * | 2018-02-02 | 2019-08-08 | EMC IP Holding Company LLC | Tracking status and restarting distributed replication |
-
2019
- 2019-09-18 CN CN201910879434.6A patent/CN110673936B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040143607A1 (en) * | 2001-06-05 | 2004-07-22 | Silicon Graphics, Inc. | Recovery and relocation of a distributed name service in a cluster filesystem |
| CN102385536A (en) * | 2010-08-27 | 2012-03-21 | 中兴通讯股份有限公司 | Method and system for realization of parallel computing |
| US20130219224A1 (en) * | 2012-02-17 | 2013-08-22 | Nec Corporation | Job continuation management apparatus, job continuation management method and job continuation management program |
| CN106095606A (en) * | 2016-06-12 | 2016-11-09 | 北京三快在线科技有限公司 | A kind of software fault treating method and apparatus of server |
| CN106547613A (en) * | 2016-10-20 | 2017-03-29 | 西北工业大学 | The scheduling of task handling process and fault recovery method |
| US20190243702A1 (en) * | 2018-02-02 | 2019-08-08 | EMC IP Holding Company LLC | Tracking status and restarting distributed replication |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110515718A (en) * | 2019-08-30 | 2019-11-29 | 深圳前海微众银行股份有限公司 | Batch tasks breakpoint is continuous to make method, apparatus, equipment and medium |
| CN110825391A (en) * | 2019-10-31 | 2020-02-21 | 北京金山云网络技术有限公司 | Service management method, device, electronic equipment and storage medium |
| CN112527484A (en) * | 2020-12-17 | 2021-03-19 | 平安银行股份有限公司 | Workflow breakpoint continuous running method and device, computer equipment and readable storage medium |
| CN112527484B (en) * | 2020-12-17 | 2024-05-10 | 平安银行股份有限公司 | Workflow breakpoint continuous running method and device, computer equipment and readable storage medium |
| CN113297081A (en) * | 2021-05-26 | 2021-08-24 | 北京京东振世信息技术有限公司 | Execution method and device of continuous integration assembly line |
| CN116339958A (en) * | 2023-05-30 | 2023-06-27 | 支付宝(杭州)信息技术有限公司 | Task execution method, device and equipment |
| CN116339958B (en) * | 2023-05-30 | 2023-09-08 | 支付宝(杭州)信息技术有限公司 | Task execution method, device and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110673936B (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110673936B (en) | Breakpoint continuous operation method and device for arrangement service, storage medium and electronic equipment | |
| EP4006731B1 (en) | Method, apparatus, device, storage medium and computer program product for testing code | |
| CN110058920B (en) | Virtual machine performance detection method and device, electronic equipment and storage medium | |
| CN111538659B (en) | Interface testing method, system, electronic equipment and storage medium of business scene | |
| CN112465466A (en) | Flow task execution method and device, computer equipment and storage medium | |
| US11169910B2 (en) | Probabilistic software testing via dynamic graphs | |
| EP4224317A1 (en) | Method and apparatus for controlling distributed operation system, and device, medium and program product | |
| CN110716843B (en) | System fault analysis processing method and device, storage medium and electronic equipment | |
| CN109299124B (en) | Method and apparatus for updating a model | |
| CN108241543B (en) | Method, service server and system for executing service operation breakpoint | |
| CN113238815A (en) | Interface access control method, device, equipment and storage medium | |
| CN114706622B (en) | Method, device, equipment, medium and product for starting model service | |
| CN110717315A (en) | System data batch modification method and device, storage medium and electronic equipment | |
| CN110609786A (en) | Software testing method and device, computer equipment and storage medium | |
| CN115840691A (en) | Remote repair of crash processes | |
| CN116324726A (en) | Accelerated non-volatile memory device inspection and forensics | |
| CN111176718A (en) | Script online method and device, storage medium and electronic equipment | |
| CN110633183B (en) | Method and related device for monitoring execution progress of software product | |
| CN113626332B (en) | Debugging method, device, equipment, storage medium and computer program product | |
| CN111522737B (en) | Automatic test verification method and device for front-end interface and storage medium | |
| CN112416695B (en) | Global variable monitoring method, device, equipment and storage medium | |
| CN114430300A (en) | Method, system, device and medium for testing wireless communication module | |
| CN115599682A (en) | Environment availability detection method, device, equipment and storage medium | |
| CN115878362A (en) | Operating system abnormity positioning method, device, equipment and storage medium | |
| CN111626770A (en) | Crowd calculation control method, system, device and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |