CN113434323A - Task flow control method of data center station and related device - Google Patents
Task flow control method of data center station and related device Download PDFInfo
- Publication number
- CN113434323A CN113434323A CN202110721920.2A CN202110721920A CN113434323A CN 113434323 A CN113434323 A CN 113434323A CN 202110721920 A CN202110721920 A CN 202110721920A CN 113434323 A CN113434323 A CN 113434323A
- Authority
- CN
- China
- Prior art keywords
- task
- node
- execution
- task node
- context information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000003860 storage Methods 0.000 claims description 19
- 230000001960 triggered effect Effects 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 14
- 238000011144 upstream manufacturing Methods 0.000 abstract description 44
- 230000008569 process Effects 0.000 abstract description 9
- 238000012423 maintenance Methods 0.000 abstract description 7
- 238000013024 troubleshooting Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 16
- 230000006870 function Effects 0.000 description 8
- 238000004140 cleaning Methods 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000002159 abnormal effect Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 230000007246 mechanism Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000013515 script Methods 0.000 description 2
- 125000002015 acyclic group Chemical group 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000013075 data extraction Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0793—Remedial or corrective actions
-
- 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/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Quality & Reliability (AREA)
- Debugging And Monitoring (AREA)
Abstract
In the embodiment of the present application, each task node executes a task based on context information generated by an upstream node, where the context information is used to describe an execution status of the upstream node, and may include information such as an execution state and an execution result, for example. Thus, the downstream node may analyze whether to perform an alarm operation or continue to perform a task based on the context information. Based on the context information, the execution of the alarm operation is completed inside each node in the task flow execution process, so that problems can be found in time to alarm, operation and maintenance personnel are informed to perform troubleshooting in time, and the normal execution of the task flow is ensured.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a method and a related apparatus for controlling task flow of a data center.
Background
The data center station can be compatible with multi-source heterogeneous data, the service flow is uniformly managed, and the service flow of the data center station can support various services. The data center can reduce the cost of repeated construction and can also keep the differentiated competitive advantages of enterprises. The stable and efficient data center station can effectively improve the service processing efficiency.
In the process of data middle station construction, mass data are acquired, calculated, stored and processed through a big data technology, and meanwhile, the data are unified and standardized. After the data are unified by the data center, standard data can be formed and stored, a large data asset layer is formed, and efficient data service is provided. To achieve various business requirements, a series of task streams are run on the data console, and each task stream contains various different types of tasks, such as SQL (Structured Query Language) class, script class, and ETL (Extract-Transform-Load) class.
An upstream and downstream dependency relationship exists between the tasks, and the downstream task is triggered to execute after the upstream task is executed successfully. The dependencies between tasks may be complex or simple, and the execution of different tasks in a task flow depends on different nodes. When a task node is abnormal, the normal execution of the downstream node is affected. Therefore, an efficient and timely early warning mechanism is needed, when the task is abnormal, operation and maintenance personnel are notified to conduct troubleshooting in time, and normal execution of the task flow is guaranteed.
Disclosure of Invention
The embodiment of the application provides a task flow control method and a related device for a data relay station, which are used for solving the problem that the normal execution of a downstream node is influenced when a certain task node is abnormal in the related technology.
In a first aspect, the present application provides a method for controlling task flow of a station in data, the method including:
the first task node determines an operation type based on the context information of the second task node, wherein the operation type comprises continuing to execute the service flow or executing the alarm operation; the first task node is a downstream node of the second task node, and the context information is used for describing a task execution state of the second task node;
the first task node determines an operation type based on the context information of the second task node, wherein the operation type comprises continuing to execute the service flow or executing the alarm operation; the first task node is a downstream node of the second task node, and the context information is used for describing a task execution status of the second task node.
Optionally, the context information is generated and stored based on a task execution result when the second task node finishes executing the task;
if the second task node is a father node, the second task node triggers to execute a task based on a preset trigger rule;
and if the second task node is a child node, the second task node triggers to execute a task based on the context information of a third task node.
Optionally, the first task node executes a task based on the operation type, including:
the first task node executes a task corresponding to the type of the first task node based on the context information of the second task node in accordance with the type of the first task node.
Optionally, the executing, according to the type of the first task node, a task corresponding to the type of the first task node based on the context information of the second task node includes:
if the type of the first task node is a branch node, judging whether the execution condition of any downstream node in a plurality of downstream nodes of the first task node is met or not based on the context information of the second task node, and if so, triggering the downstream node meeting the execution condition to execute the task;
and if the execution conditions of all the downstream nodes are not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the executing, according to the type of the first task node, a task corresponding to the type of the first task node based on the context information of the second task node includes:
if the type of the first task node is a merging node and the first task node determines that the execution of the second task node fails based on the context information, the first task node determines whether a merging condition for triggering a downstream node is met based on an execution result in the context information, and if the merging condition is met, the downstream node is triggered to continue executing the task;
and if the merging condition is not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the executing, according to the type of the first task node, a task corresponding to the type of the first task node based on the context information of the second task node includes:
if the type of the first task node is a quality check node, the first task node acquires an execution result of the second task node included in the context information;
identifying whether the execution result meets the standard requirement;
and if the standard requirements are not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the preset triggering alarm rule supports customization.
Optionally, the context information includes: execution state, execution time, and execution result.
In a second aspect, the present application provides a task flow control apparatus for a data center, applied to a first task node, the apparatus including:
the operation type determining module is used for determining an operation type based on the context information of the second task node, wherein the operation type comprises the operation of continuously executing the service flow or the alarm operation; the first task node is a downstream node of the second task node, and the context information is used for describing a task execution state of the second task node;
and the execution module is used for executing tasks based on the operation types.
Optionally, the context information is generated and stored based on a task execution result when the second task node finishes executing the task; if the second task node is a father node, the second task node triggers to execute a task based on a preset trigger rule;
and if the second task node is a child node, the second task node triggers to execute a task based on the context information of a third task node.
Optionally, the execution module is specifically configured to:
executing a task corresponding to the type of the first task node based on the context information of the second task node in accordance with the type of the first task node.
Optionally, the execution module is specifically configured to:
if the type of the first task node is a branch node, judging whether the execution condition of any downstream node in a plurality of downstream nodes of the first task node is met or not based on the context information of the second task node, and if so, triggering the downstream node meeting the execution condition to execute the task;
and if the execution conditions of all the downstream nodes are not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the execution module is specifically configured to:
if the type of the first task node is a merging node and the first task node determines that the execution of the second task node fails based on the context information, determining whether a merging condition triggering a downstream node is met based on an execution result in the context information, and if the merging condition is met, triggering the downstream node to continue executing the task;
and if the merging condition is not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the execution module is specifically configured to:
if the type of the first task node is a quality check node, acquiring an execution result of the second task node included in the context information;
identifying whether the execution result meets the standard requirement;
and if the standard requirements are not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the preset triggering alarm rule supports customization.
Optionally, the context information includes: execution state, execution time, and execution result.
In a third aspect, the present application further provides an electronic device, including:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement any of the methods as provided in the first aspect of the application.
In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where instructions, when executed by a processor of an electronic device, enable the electronic device to perform any one of the methods as provided in the first aspect of the present application.
In a fifth aspect, an embodiment of the present application provides a computer program product comprising a computer program that, when executed by a processor, implements any of the methods as provided in the first aspect of the present application.
The technical scheme provided by the embodiment of the application at least has the following beneficial effects:
in the embodiment of the present application, each task node executes a task based on context information generated by an upstream node, where the context information is used to describe an execution status of the upstream node, and for example, the context information may include information such as an execution state and an execution result. Thus, the downstream node may analyze whether to perform an alarm operation or continue to perform a task based on the context information. Based on the context information, the execution of the alarm operation is completed inside each node in the task flow execution process, so that problems can be found in time to alarm, operation and maintenance personnel are informed to perform troubleshooting in time, and the normal execution of the task flow is 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 disclosure.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of task flow control of a data center according to an embodiment of the present application;
FIGS. 2-5 are schematic diagrams illustrating a flow control process of task flow of a data center according to an embodiment of the present application;
FIG. 6 is a diagram illustrating an example of task flow control of a data center according to an embodiment of the present application;
FIG. 7 is a diagram illustrating an example of task flow control of a data center according to an embodiment of the present application;
FIG. 8 is a diagram illustrating an example of task flow control of a data center according to an embodiment of the present application;
FIG. 9 is a block diagram illustrating a task flow control apparatus of a station in data according to an exemplary embodiment;
FIG. 10 is a block diagram illustrating an electronic device for task flow control of stations in data according to an example embodiment.
Detailed Description
In order to make the technical solutions of the present application better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.
(1) In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.
(2) "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
(3) A server serving the terminal, the contents of the service such as providing resources to the terminal, storing terminal data; the server is corresponding to the application program installed on the terminal and is matched with the application program on the terminal to run.
(4) The terminal device may refer to an APP (Application) of a software class, or may refer to a client. The system is provided with a visual display interface and can interact with a user; is corresponding to the server, and provides local service for the client. For software applications, except some applications that are only run locally, the software applications are generally installed on a common client terminal and need to be run in cooperation with a server terminal. After the development of the internet, more common application programs include short video applications, email clients for receiving and sending emails, and clients for instant messaging, for example. For such applications, a corresponding server and a corresponding service program are required in the network to provide corresponding services, such as database services, configuration parameter services, and the like, so that a specific communication connection needs to be established between the client terminal and the server terminal to ensure the normal operation of the application program.
(5) And the task nodes comprise a plurality of task nodes in the same task flow, execute corresponding tasks and have dependency relationships among different task nodes. For example, a task flow may include a parent node and a child node, and a parent node may include a plurality of child nodes. The triggering of each child node, except the parent node, is dependent on the upstream node on which it depends. For example, a task node includes, in parent-child order: task node 1-task node 2-task node 3. After the task node 1 finishes the task, the task node 2 continues to execute the task according to the execution result of the task node 1. The task node 3 executes the task depending on the execution result of the task node 2. It should be noted that one child node may depend on multiple upstream nodes. For example, the task node 2 may use not only the task node 1 but also the task node 4 as a parent node.
(6) The method comprises the steps that an upstream node and a downstream node are in a relative relation and used for describing the execution dependency relation of two task nodes. Continuing with the above example, task node 1 is an upstream node of task node 2, and task node 2 is a downstream node of task node 1. Similarly, the task node 2 is an upstream node of the task node 3, and the task node 3 is a downstream node of the task node 2. It should be understood that the same task node may have multiple upstream nodes, and may also have multiple downstream nodes.
(7) The execution state of the task node and the final result of the task node execution comprise success, failure and non-execution states:
the success is as follows: the current task node is successfully triggered and successfully executed;
failure: the current task node is successfully triggered but fails to execute; such as wrong logic or grammar of task node codes, overtime task execution, and incapability of acquiring enough execution resources in the task node execution process;
not executing: the current task node is not triggered. Such as a parent node failing execution or the current node being a node downstream of the branch node and the branch condition not being satisfied.
(8) And the context information of the task node is used for describing the description of the task node on the execution state of the task executed at this time. For example, may include execution state, execution time, execution result, and the like. The context information can be defined according to different tasks, and is applicable to the embodiment of the application.
A huge amount of task flows need to be processed on the station in the data. The same task flow comprises a plurality of tasks needing to be executed, the different tasks have upstream and downstream dependency relationships, and the upstream task is triggered to execute after being successfully executed. The dependencies between tasks may be complex or simple, and the execution of different tasks in a task flow depends on different nodes. When a task node is abnormal, the normal execution of the downstream node is affected. Therefore, an efficient and timely early warning mechanism is needed, when the task is abnormal, operation and maintenance personnel are notified to conduct troubleshooting in time, and normal execution of the task flow is guaranteed.
In view of the above, the present application provides a method and a related apparatus for controlling task flow of a data center station. In the embodiment of the present application, each task node executes a task based on context information generated by an upstream node, where the context information is used to describe an execution status of the upstream node, and for example, the context information may include information such as an execution state and an execution result. Thus, the downstream node may analyze whether to perform an alarm operation or continue to perform a task based on the context information. Based on the context information, the execution of the alarm operation is completed inside each node in the task flow execution process, so that problems can be found in time to alarm, operation and maintenance personnel are informed to perform troubleshooting in time, and the normal execution of the task flow is ensured.
Fig. 1 is a schematic diagram of an application scenario of task flow control of a station in data according to an embodiment of the present application. The application scenario includes a plurality of terminal devices 101 (including terminal device 101-1, terminal device 101-2, … … terminal device 101-n), and further includes server 102. The terminal device 101 and the server 102 are connected via a wireless or wired network, and the terminal device 101 includes but is not limited to a desktop computer, a mobile phone, a mobile computer, a tablet computer, a media player, a smart wearable device, a smart television, and other electronic devices. The server 102 may be a server, a server cluster composed of several servers, or a cloud computing center. The server 102 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a network service, cloud communication, middleware service, a domain name service, a security service, a CDN, a big data and artificial intelligence platform, and the like.
The task nodes may be configured in the server 102. One task node or a plurality of task nodes may be included in the same server 102 and are suitable for use in embodiments of the present application.
When any task node finishes a task, generating context information for describing the execution state, the execution time consumption, the execution result and the like of the task node. Therefore, the downstream node can judge whether to continue executing the task or trigger the alarm according to the context information of the upstream node. Therefore, the alarm operation is dispersedly completed in different task nodes, and the problems can be found and the alarm can be given in time. After the server alarms, the alarm may be sent to the terminal device 101 so that the operation and maintenance personnel can find the problem in time.
In the embodiment of the present application, different task nodes may be developed by developers. For example, the following classes of nodes may be included.
1. And the ETL node is used for importing the data in the service generator into the data operation layer.
2. Developing class nodes, compiling SQL, Python or spark Jar codes based on the original data of the data warehouse, cleaning, calculating and processing the data, and storing the data in a data warehouse layer.
The regularly scheduled traffic typically contains ETL nodes and development class nodes. And importing the data of the service generator into a data operation layer (ODS layer) through the ETL node at regular time or in real time. The data operation layer is the layer closest to the service data.
And cleaning, calculating and processing the ODS layer data through the development class node, and storing the ODS layer data into the data warehouse layer. The data warehouse layer is divided into a data detail layer, a data intermediate layer and a data service layer according to the data service scene.
In the data extraction and processing calculation process in the prior art, the problems that the execution failure of a certain node causes that the subsequent node cannot be executed, the alarm mechanism is delayed, and the idle running of the downstream node causes invalid resource occupation due to no data of the upstream node exist. Therefore, the application provides some task nodes, such as branch nodes and merge nodes, to improve the execution efficiency of the traffic flow.
3. And the branch node refers to the calculation output result of the upstream node or influences the number of data pieces. In the embodiment of the application, the branch node can be configured with a plurality of user-defined branches. Each custom branch definition contains a decision condition referencing a parameter and a corresponding downstream branch. And when the branch nodes are triggered, judging whether the branch conditions are met one by one, and if so, triggering the corresponding downstream nodes to execute the tasks.
4. And the merging node refers to the execution state of the upstream node and configures a merging condition containing the reference parameter. And when the merging node is triggered, judging whether the merging condition is met, if so, triggering the downstream node, otherwise, failing to merge, and skipping to operate the downstream node.
There may be one or more upstream nodes of the merge node. When the merging node has an upstream node: the upstream node executes the fault, and the merge node defines a merge condition for the upstream fault, at which point the node triggers a downstream alarm or exception handling (e.g., rollback of exception data). The problems of alarm and exception handling of the failed node are solved.
When the merging node has a plurality of upstream nodes: the upstream node is a branch node downstream node, and is plural. Since a branch node triggers only one branch downstream node, only one node is triggered when there are more upstream nodes. At this time, a merging condition for successful execution of a node is defined, and the problem of dependence triggering of a branch downstream node is solved.
Of course, it should be understood that the types of task nodes that can be developed are not limited to the above nodes, and other task nodes can be added according to actual needs when implemented.
After the task nodes are developed, the task nodes can be arranged according to different task flow requirements, so that the task nodes can cooperate to complete task processing. For example, in implementation, task orchestration may be performed according to the dependency and the sequence of the node tasks, and a directed acyclic task flow is created.
After the task stream is created, the tasks may be performed by the task nodes. Referring to fig. 2, a schematic flow chart of task flow control of a station in data is provided according to an embodiment of the present application, including the following steps:
and if the first task node is a downstream node of the second task node, the first task node generates and stores context information after the task is executed each time. The context information is used for describing the task execution status of the second task node. As such, for the first task node, the first task node may determine the operation type based on the context information of the second task node in step 201. Then, in step 202, the first task performs a task based on the operation type.
Thus, context information about the execution conditions is available to downstream nodes. So that the downstream node determines whether to alert or continue to perform a task based on the context information of the upstream node. On one hand, the failure of task execution can be guaranteed, and timely alarming can be realized, on the other hand, the task can be automatically executed based on the context information, and the normal operation of the task can be guaranteed as far as possible.
In some embodiments, the context information may include execution state, execution time consumption, execution result, and the like. In specific implementation, the content contained in the context information of different task nodes can be configured according to the service requirement. Based on the execution state in the context information, the downstream node can know the execution state of the upstream node conveniently, and based on the execution result, the subsequent service logic, such as alarm identification, can be realized. Based on the execution time consumption, the downstream node can be helped to understand the time consumption cost of the upstream node for executing the task so as to execute the corresponding decision. The content covered by the context information of different task nodes can be configured according to the needs of the task node and its downstream nodes, which is not limited in this application.
In implementation, if the second task node is a father node, the second task node triggers to execute a task based on a pre-configured trigger rule; and if the second task node is a child node, the second task node triggers and executes a task based on the context information of a third task node, wherein the second task node is a downstream node of the third task node. That is, in the embodiment of the present application, the identity of any task node is not fixed, and any task node may be an upstream node of a downstream node, and is used to generate context information for storage when a task is executed. Or the downstream node of the upstream node, for analyzing and processing the context information of the upstream node to determine whether to continue to execute the task or execute the alarm operation.
In the embodiment of the present application, the trigger rule preconfigured for the parent node may be configured according to actual requirements, for example, a timing trigger rule may be configured, for example, backup, update, statistics, and the like are completed on data of the current day at 0 point in the morning every day. The specific trigger rule may be configured according to actual requirements, and is not limited in this application. It should be noted that the trigger rule can be flexibly configured by a developer according to the business requirement. And the user of the data center station can flexibly configure according to the needs of the user.
In some embodiments, multiple types of task nodes may be added to the present application, for example, as set forth above, the types of task nodes may include branch nodes, merge nodes, and quality check nodes. In implementation, the first task node may execute a task corresponding to the type of the first task node based on the context information of the second task node according to the type of the first task node. Therefore, different task nodes can determine respective tasks according to different work division of the nodes so as to find problems in time and give an alarm.
1) And aiming at the branch node:
as shown in fig. 3, the method comprises the following steps:
in step 301, if the type of the first task node is a branch node, determining whether an execution condition of any downstream node of a plurality of downstream nodes of the first task node is satisfied based on the context information of the second task node;
in step 302, if yes, triggering the downstream node meeting the execution condition to execute the task; and if the execution conditions of all the downstream nodes are not met, executing alarm operation based on a preset alarm triggering rule.
In practice, the downstream node of the branch node includes a plurality of nodes. Thus, the branch node may analyze the task context of the upstream node in order to determine which downstream node to trigger or whether an alarm is required. Therefore, the problem can be found in time. And triggering the downstream nodes capable of executing the tasks to execute the tasks, so as to further ensure the normal operation of the tasks.
It should be understood that the execution conditions of the branch nodes of different tasks can be flexibly configured according to the service requirements, which is not limited in the present application.
2) Aiming at the merging node:
as shown in fig. 4, the method comprises the following steps:
in step 401, if the type of the first task node is a merge node and the first task node determines that the second task node fails to execute based on the context information, the first task node determines whether a merge condition triggering a downstream node is satisfied based on an execution result in the context information.
In step 402, if the merging condition is satisfied, the downstream node is triggered to continue executing the task.
In step 403, if the merging condition is not satisfied, an alarm operation is performed based on a preset alarm triggering rule.
For example, the upstream node fails to execute, and the merge node may analyze the context information of the upstream node in order to determine whether the task flow may continue to execute. The merging condition for determining whether to continue execution may be configured according to the service requirement, which is not limited in this application.
When the execution can be continued, the service flow can be triggered to be continued, and the task completion rate of the service flow is improved. The problem that in the related technology, the task execution of the upstream node fails, and the task completion rate is low because the task execution can only be stopped is solved.
In addition, under the condition that the task execution of the upstream node fails, the merging node can automatically find out the timely alarm, and the normal execution of the task flow is ensured.
3) And aiming at the quality check node:
as shown in fig. 5, the method comprises the following steps:
in step 501, if the type of the first task node is a quality check node, the first task node obtains an execution result of the second task node included in the context information;
in step 502, identifying whether the execution result meets the standard requirement;
in step 502, if the standard requirement is not met, based on the preset triggering alarm rule, an alarm operation is executed.
Of course, if the standard requirement is met, the downstream node can be continuously triggered to continuously execute the task.
In the embodiment of the application, the quality check node finishes the judgment on whether the data meets the marking requirement, can timely find the problem of the execution failure of the downstream node caused by the fact that the data does not meet the standard, and improves the execution efficiency of the task flow.
In some embodiments, the internal preset trigger alarm rules support customization no matter what type of task node. For example, SQL and other scripts can be used for writing triggering alarm rules to realize early warning based on business data. For example, the triggering alarm rules may define the content of the alarm message under different triggering conditions. For example, for a branch node, it may be determined which downstream nodes can continue to execute the task and which downstream nodes cannot continue to execute the task, and then downstream node information that cannot execute the task, downstream node information that can continue to execute the task, and context information of an upstream node of the branch node may be covered in the alarm message. So that the operation and maintenance task can know the execution condition of the service flow according to the content of the alarm message.
For the sake of understanding, the following describes the task flow control method of the data center station provided in the embodiments of the present application with some specific examples.
Example 1: branch node implementation task flow execution optimization
As shown in fig. 6, it is assumed that the task nodes include a data integration node, a branch node, and a data cleansing node.
The data integration node: data generated by a service generator is imported into an ODS layer (Operational Data Store, Data operation layer).
And the branch node is used for judging the branch _ influence line number, can refer to the data influence number of the data integration node at the upstream and configures the downstream branch. And when the number of the influencing nodes is not 0, executing the downstream data cleaning nodes, and when the number of the influencing nodes is 0, triggering the downstream sending early warning nodes.
And (3) data cleaning nodes: for the SQL node, the Data of the ODS layer (Data operation layer) is calculated, processed, and filtered, and then imported into the DWD layer (Data water Detail layer).
Sending an early warning: and sending early warning information to an alarm center.
Therefore, the branch node can realize data abnormity early warning based on the embodiment. In addition, the data integration node can effectively determine whether to perform data cleaning or warning based on the number of the affected data pieces, and the task execution flow can be optimized.
Example 2: quality check node for realizing data quality early warning
As shown in fig. 7:
and (3) data cleaning nodes: for the SQL node, the data of the ODS layer (data operation layer) is calculated, processed, and filtered, and then imported into the DWD layer (data detail layer).
Quality check node: for the SQL node, whether the data in the DWD layer (data detail layer) meets the standard is checked.
Branch _ quality check whether the node passes: and a check result of the upstream SQL node can be quoted, and if the check result is failure, the downstream early warning node is triggered.
Early warning node: and sending early warning information to an alarm center.
Therefore, in the embodiment, the identification of the non-standard data is realized, and the alarm is triggered in time.
Example 3: merging node implementation failure task early warning
As shown in fig. 8:
and (3) data cleaning nodes: the SQL node calculates, processes, and filters data in the ODS layer (data operation layer), and then imports the data into the DWD layer (data detail layer).
And the merging node triggers a downstream sending early warning node when the execution of a certain node of the upstream node fails.
Sending an early warning: and sending early warning information to an alarm center.
Therefore, in the embodiment, the merging node can find the problem of the upstream node in time and trigger the alarm in time.
In summary, the method and the device directly introduce the node context and the flow control node into the service flow, store the execution ending state of the task, the execution time consumption and the number of the influence data into the node context, judge the execution information of the upstream node in the context through the branch and merge nodes, and perform reasonable optimization and early warning. Meanwhile, the execution result of the node is stored in the context, and the flow control based on the service code can be realized by self-defining logic in SQL and other nodes.
During early warning, whether the early warning information is sent or not is judged by the task, a monitoring module is not needed to inquire regularly, and the pressure of a scheduling system is effectively reduced.
The embodiment of the application also provides a task flow control device of the data center station based on the same inventive concept. Fig. 9 is a block diagram illustrating a task flow control apparatus of a station in data according to an exemplary embodiment, applied to a first task node, and referring to fig. 9, the apparatus 900 includes:
an operation type determining module 901, configured to determine an operation type based on the context information of the second task node, where the operation type includes continuing to execute a service flow or executing an alarm operation; the first task node is a downstream node of the second task node, and the context information is used for describing a task execution state of the second task node;
an executing module 902, configured to execute a task based on the operation type.
Optionally, the context information is generated and stored based on a task execution result when the second task node finishes executing the task; if the second task node is a father node, the second task node triggers to execute a task based on a preset trigger rule;
and if the second task node is a child node, the second task node triggers to execute a task based on the context information of a third task node.
Optionally, the execution module is specifically configured to:
executing a task corresponding to the type of the first task node based on the context information of the second task node in accordance with the type of the first task node.
Optionally, the execution module is specifically configured to:
if the type of the first task node is a branch node, judging whether the execution condition of any downstream node in a plurality of downstream nodes of the first task node is met or not based on the context information of the second task node, and if so, triggering the downstream node meeting the execution condition to execute the task;
and if the execution conditions of all the downstream nodes are not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the execution module is specifically configured to:
if the type of the first task node is a merging node and the first task node determines that the execution of the second task node fails based on the context information, determining whether a merging condition triggering a downstream node is met based on an execution result in the context information, and if the merging condition is met, triggering the downstream node to continue executing the task;
and if the merging condition is not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the execution module is specifically configured to:
if the type of the first task node is a quality check node, acquiring an execution result of the second task node included in the context information;
identifying whether the execution result meets the standard requirement;
and if the standard requirements are not met, executing alarm operation based on a preset alarm triggering rule.
Optionally, the preset triggering alarm rule supports customization.
Optionally, the context information includes: execution state, execution time, and execution result.
Having described the task flow control and apparatus of the data center station of an exemplary embodiment of the present application, next, an electronic device according to another exemplary embodiment of the present application is described.
As will be appreciated by one skilled in the art, aspects of the present application may be embodied as a system, method or program product. Accordingly, various aspects of the present application 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.
In some possible implementations, an electronic device according to the present application may include at least one processor, and at least one memory. Wherein the memory stores program code which, when executed by the processor, causes the processor to perform the method for task flow control of a station in data according to various exemplary embodiments of the present application described above in this specification. For example, the processor may perform steps in a method of task flow control as a station in data.
The electronic apparatus 130 according to this embodiment of the present application is described below with reference to fig. 10. The electronic device 130 shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present application.
As shown in fig. 10, the electronic device 130 is represented in the form of a general electronic device. The components of the electronic device 130 may include, but are not limited to: the at least one processor 131, the at least one memory 132, and a bus 133 that connects the various system components (including the memory 132 and the processor 131).
The memory 132 may include readable media in the form of volatile memory, such as Random Access Memory (RAM)1321 and/or cache memory 1322, and may further include Read Only Memory (ROM) 1323.
The electronic device 130 may also communicate with one or more external devices 134 (e.g., keyboard, pointing device, etc.), with one or more devices that enable a user to interact with the electronic device 130, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 130 to communicate with one or more other electronic devices. Such communication may occur via input/output (I/O) interfaces 135. Also, the electronic device 130 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 136. As shown, network adapter 136 communicates with other modules for electronic device 130 over bus 133. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with electronic device 130, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
In an exemplary embodiment, a computer-readable storage medium comprising instructions, such as memory 132 comprising instructions, executable by processor 131 of apparatus 700 or processor 131 of apparatus 800 to perform task flow control of stations in the data is also provided. Alternatively, the storage medium may be a non-transitory computer readable storage medium, which may be, for example, a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In an exemplary embodiment, a computer program product is also provided, comprising a computer program which, when executed by the processor 131, implements any of the methods of task flow control for stations in data as provided herein.
In an exemplary embodiment, the various aspects of the task flow control of a station in data provided by the present application may also be embodied in the form of a program product comprising program code means for causing a computer device to perform the steps of the method for task flow control of a station in data according to various exemplary embodiments of the present application described above in this specification, when the program product is run on the computer 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.
The program product for task flow control of a data center station of embodiments of the present application may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be executable on an electronic device. However, the program product of the present application is not limited thereto, and in this 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.
A 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 any of a variety of 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 of the present application 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 consumer electronic device, partly on the consumer electronic device, as a stand-alone software package, partly on the consumer electronic device and partly on a remote electronic device, or entirely on the remote electronic device or server. In the case of remote electronic devices, the remote electronic devices may be connected to the consumer electronic device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external electronic device (e.g., through the internet using an internet service provider).
It should be noted that although several units or sub-units of the apparatus are mentioned in the above detailed description, such division is merely exemplary and not mandatory. Indeed, the features and functions of two or more units described above may be embodied in one unit, according to embodiments of the application. Conversely, the features and functions of one unit described above may be further divided into embodiments by a plurality of units.
Further, while the operations of the methods of the present application are depicted in the drawings in a particular order, this does not require or imply that these operations must be performed in this particular order, or that all of the illustrated operations 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.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may 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, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable image scaling apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable image scaling apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (19)
1. A method for controlling task flow of a station in data, the method comprising:
the first task node determines an operation type based on the context information of the second task node, wherein the operation type comprises continuing to execute the service flow or executing the alarm operation; the first task node is a downstream node of the second task node, and the context information is used for describing a task execution state of the second task node;
the first task node executes a task based on the operation type.
2. The method according to claim 1, wherein the context information is generated and saved by the second task node based on task execution results when the second task node finishes executing the task;
if the second task node is a father node, the second task node triggers to execute a task based on a preset trigger rule;
and if the second task node is a child node, the second task node triggers to execute a task based on the context information of a third task node.
3. The method of claim 1, wherein the first task node performs a task based on the operation type, comprising:
the first task node executes a task corresponding to the type of the first task node based on the context information of the second task node in accordance with the type of the first task node.
4. The method according to claim 3, wherein performing the task corresponding to the type of the first task node based on the context information of the second task node according to the type of the first task node comprises:
if the type of the first task node is a branch node, judging whether the execution condition of any downstream node in a plurality of downstream nodes of the first task node is met or not based on the context information of the second task node, and if so, triggering the downstream node meeting the execution condition to execute the task;
and if the execution conditions of all the downstream nodes are not met, executing alarm operation based on a preset alarm triggering rule.
5. The method according to claim 3, wherein performing the task corresponding to the type of the first task node based on the context information of the second task node according to the type of the first task node comprises:
if the type of the first task node is a merging node and the first task node determines that the execution of the second task node fails based on the context information, the first task node determines whether a merging condition for triggering a downstream node is met based on an execution result in the context information, and if the merging condition is met, the downstream node is triggered to continue executing the task;
and if the merging condition is not met, executing alarm operation based on a preset alarm triggering rule.
6. The method according to claim 3, wherein performing the task corresponding to the type of the first task node based on the context information of the second task node according to the type of the first task node comprises:
if the type of the first task node is a quality check node, the first task node acquires an execution result of the second task node included in the context information;
identifying whether the execution result meets the standard requirement;
and if the standard requirements are not met, executing alarm operation based on a preset alarm triggering rule.
7. The method according to any of claims 4-6, wherein the preset trigger alarm rules support customization.
8. The method of claim 1, wherein the context information comprises: execution state, execution time, and execution result.
9. A task flow control apparatus for a station in data, applied to a first task node, the apparatus comprising:
the operation type determining module is used for determining an operation type based on the context information of the second task node, wherein the operation type comprises the operation of continuously executing the service flow or the alarm operation; the first task node is a downstream node of the second task node, and the context information is used for describing a task execution state of the second task node;
and the execution module is used for executing tasks based on the operation types.
10. The apparatus according to claim 9, wherein the context information is generated and saved by the second task node based on task execution results at the end of executing a task; if the second task node is a father node, the second task node triggers to execute a task based on a preset trigger rule;
and if the second task node is a child node, the second task node triggers to execute a task based on the context information of a third task node.
11. The apparatus of claim 9, wherein the execution module is specifically configured to:
executing a task corresponding to the type of the first task node based on the context information of the second task node in accordance with the type of the first task node.
12. The apparatus of claim 11, wherein the execution module is specifically configured to:
if the type of the first task node is a branch node, judging whether the execution condition of any downstream node in a plurality of downstream nodes of the first task node is met or not based on the context information of the second task node, and if so, triggering the downstream node meeting the execution condition to execute the task;
and if the execution conditions of all the downstream nodes are not met, executing alarm operation based on a preset alarm triggering rule.
13. The apparatus of claim 11, wherein the execution module is specifically configured to:
if the type of the first task node is a merging node and the first task node determines that the execution of the second task node fails based on the context information, determining whether a merging condition triggering a downstream node is met based on an execution result in the context information, and if the merging condition is met, triggering the downstream node to continue executing the task;
and if the merging condition is not met, executing alarm operation based on a preset alarm triggering rule.
14. The apparatus of claim 11, wherein the execution module is specifically configured to:
if the type of the first task node is a quality check node, acquiring an execution result of the second task node included in the context information;
identifying whether the execution result meets the standard requirement;
and if the standard requirements are not met, executing alarm operation based on a preset alarm triggering rule.
15. The apparatus according to any of claims 12-14, wherein the preset trigger alarm rules support customization.
16. The apparatus of claim 9, wherein the context information comprises: execution state, execution time, and execution result.
17. An electronic device, comprising:
a processor;
a memory for storing the processor-executable instructions;
wherein the processor is configured to execute the instructions to implement the method of task flow control of a station in data according to any of claims 1-8.
18. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method for task flow control of a station in data according to any of claims 1-8.
19. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the method for task flow control of a station in data according to any of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110721920.2A CN113434323A (en) | 2021-06-28 | 2021-06-28 | Task flow control method of data center station and related device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110721920.2A CN113434323A (en) | 2021-06-28 | 2021-06-28 | Task flow control method of data center station and related device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113434323A true CN113434323A (en) | 2021-09-24 |
Family
ID=77757344
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110721920.2A Pending CN113434323A (en) | 2021-06-28 | 2021-06-28 | Task flow control method of data center station and related device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113434323A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113918298A (en) * | 2021-10-12 | 2022-01-11 | 北京字节跳动网络技术有限公司 | Method, system and equipment for processing multimedia data |
| WO2024046130A1 (en) * | 2022-08-31 | 2024-03-07 | 中兴通讯股份有限公司 | Task processing method, electronic device, and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102902574A (en) * | 2012-09-24 | 2013-01-30 | 东软集团股份有限公司 | Cooperative processing method and device of multiple information flow nodes |
| CN105573836A (en) * | 2016-02-23 | 2016-05-11 | 中国农业银行股份有限公司 | Data processing method and device |
| CN110333940A (en) * | 2019-06-25 | 2019-10-15 | 深圳前海微众银行股份有限公司 | Method for scheduling task, device, equipment and storage medium based on condition |
| CN110489261A (en) * | 2019-07-31 | 2019-11-22 | 上海艾融软件股份有限公司 | Task handles alarm method, device and electronic equipment, storage medium |
| CN111625679A (en) * | 2020-04-03 | 2020-09-04 | 北京奇艺世纪科技有限公司 | Method and device for generating video story line |
| CN112000453A (en) * | 2020-08-25 | 2020-11-27 | 支付宝(杭州)信息技术有限公司 | Scheduling method and system of stream computing system |
| CN112559287A (en) * | 2020-12-11 | 2021-03-26 | 万达信息股份有限公司 | Method and device for optimizing task flow in data |
-
2021
- 2021-06-28 CN CN202110721920.2A patent/CN113434323A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102902574A (en) * | 2012-09-24 | 2013-01-30 | 东软集团股份有限公司 | Cooperative processing method and device of multiple information flow nodes |
| CN105573836A (en) * | 2016-02-23 | 2016-05-11 | 中国农业银行股份有限公司 | Data processing method and device |
| CN110333940A (en) * | 2019-06-25 | 2019-10-15 | 深圳前海微众银行股份有限公司 | Method for scheduling task, device, equipment and storage medium based on condition |
| CN110489261A (en) * | 2019-07-31 | 2019-11-22 | 上海艾融软件股份有限公司 | Task handles alarm method, device and electronic equipment, storage medium |
| CN111625679A (en) * | 2020-04-03 | 2020-09-04 | 北京奇艺世纪科技有限公司 | Method and device for generating video story line |
| CN112000453A (en) * | 2020-08-25 | 2020-11-27 | 支付宝(杭州)信息技术有限公司 | Scheduling method and system of stream computing system |
| CN112559287A (en) * | 2020-12-11 | 2021-03-26 | 万达信息股份有限公司 | Method and device for optimizing task flow in data |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113918298A (en) * | 2021-10-12 | 2022-01-11 | 北京字节跳动网络技术有限公司 | Method, system and equipment for processing multimedia data |
| CN113918298B (en) * | 2021-10-12 | 2024-05-14 | 北京字节跳动网络技术有限公司 | Multimedia data processing method, system and equipment |
| WO2024046130A1 (en) * | 2022-08-31 | 2024-03-07 | 中兴通讯股份有限公司 | Task processing method, electronic device, and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10805407B2 (en) | Supporting high availability for orchestrated services | |
| CN107016480B (en) | Task scheduling method, device and system | |
| US20230039566A1 (en) | Automated system and method for detection and remediation of anomalies in robotic process automation environment | |
| CN105573824B (en) | Monitoring method and system for distributed computing system | |
| US10505881B2 (en) | Generating message envelopes for heterogeneous events | |
| US11394801B2 (en) | Resiliency control engine for network service mesh systems | |
| CN103401698A (en) | Monitoring system used for alarming server status in server cluster operation | |
| US11036605B2 (en) | Feedback tuples for detecting data flow anomalies in stream computing environment | |
| CN108089915B (en) | Method and system for business control processing based on message queue | |
| CN111190892B (en) | Method and device for processing abnormal data in data backfilling | |
| CN113434323A (en) | Task flow control method of data center station and related device | |
| CN111526049B (en) | Operation and maintenance system, operation and maintenance method, electronic device and storage medium | |
| CN110611707A (en) | Task scheduling method and device | |
| US10372572B1 (en) | Prediction model testing framework | |
| CN111190732A (en) | Timed task processing system and method, storage medium and electronic device | |
| CN113760677A (en) | Abnormal link analysis method, device, equipment and storage medium | |
| CN113377626A (en) | Visual unified alarm method, device, equipment and medium based on service tree | |
| CN110781009A (en) | Method and device for real-time communication of browser page | |
| CN110798339A (en) | Task disaster tolerance method based on distributed task scheduling framework | |
| CN112860504A (en) | Monitoring method and device, computer storage medium and electronic equipment | |
| CN112600842A (en) | Cluster shell method and device, electronic equipment and computer readable storage medium | |
| CN111162938A (en) | Data processing system and method | |
| CN113419829B (en) | Job scheduling method, device, scheduling platform and storage medium | |
| CN115658248A (en) | Task scheduling method and device, electronic equipment and storage medium | |
| CN114253534A (en) | Real-time data processing method and system |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210924 |