A machine room task notification processing method, device and task notification processing system

Abstract

The application discloses a machine room task notification processing method and device and a task notification processing system. The method is executed by a master node server in the task notification processing system. Each node server of the task notification processing system is arranged in each machine room. The method comprises the following steps: receiving a machine room task notification of a machine room where the master node server is located; receiving a machine room task notification of a machine room where a slave node server is located and sent by the slave node server; performing summary processing on the received machine room task notifications; and sending the machine room task notifications after the summary processing to an external notification server connected with the master node server. The master node server in the task notification processing system performs unified summary processing on the machine room task notifications received by other node servers and then sends the machine room task notifications to corresponding external notification servers, so that the sending quantity of the task notifications is reduced, the task notifications after the summary processing are convenient for manual unified checking, and the subsequent manual operation and maintenance efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus and system for processing task notifications in a computer room. Background Technology

[0002] In distributed system applications, it's common to see multiple data centers (IDCs) simultaneously executing scheduled tasks, such as transaction reconciliation and file dumping. In these scenarios, each IDC processes its own data and, upon completion, sends out a task notification indicating whether the task was successful or failed.

[0003] However, this task notification processing method has problems such as a large number of task notifications and inconvenience in viewing task notifications, resulting in low operation and maintenance efficiency. Summary of the Invention

[0004] This application provides a data center task notification processing method, apparatus, and system to reduce the amount of task notifications and improve operational efficiency to a certain extent.

[0005] The embodiments of this application adopt the following technical solutions:

[0006] In a first aspect, embodiments of this application provide a data center task notification processing method, executed by a master node server in a task notification processing system, wherein each node server of the task notification processing system is deployed in a different data center, and the method includes:

[0007] Receive data center task notifications from the data center where the master node server is located;

[0008] Receive data center task notifications from the slave node server regarding the data center where the slave node server is located;

[0009] The received task notifications from each computer room are aggregated and processed.

[0010] The aggregated and processed data center task notifications are sent out through the external notification server connected to the master node server.

[0011] Optionally, the master node server is determined from the node servers of the task notification processing system through an election algorithm, and each slave node server stores the node information of the master node server sent based on the Gossip protocol.

[0012] The receipt of data center task notifications sent from the slave node server includes:

[0013] Receive data center task notifications sent by each slave node server based on the saved node information of the master node server.

[0014] Optionally, the method further includes:

[0015] The system responds to node status probe requests from slave nodes via the Gossip protocol, enabling each slave node to determine a new master node server through an election algorithm when it determines that the current master node server has failed based on the response to the node status probe request.

[0016] Optionally, the process of aggregating and processing the received task notifications from each computer room includes:

[0017] The interface of the data storage module connected to the master node server is called to store the task notifications of each data center into the data storage module, so as to realize the aggregation of task notifications of each data center through the data storage module.

[0018] Optionally, storing task notifications from each computer room into the data storage module includes:

[0019] Determine the identification information of the computer room task notification;

[0020] Determine whether a data storage module already contains a data center task notification corresponding to the identifier information of the data center task notification;

[0021] If it exists, the data center task notification will not be stored in the data storage module;

[0022] If it does not exist, the data center task notification will be stored in the data storage module.

[0023] Optionally, the process of aggregating and processing the received task notifications from each computer room further includes:

[0024] Determine the type of task notification for each computer room;

[0025] The task notifications from each computer room are summarized and processed according to their type.

[0026] Optionally, the aggregated data center task notification may include one or more of the following: task execution time batch, task notification name, and task execution result.

[0027] Optionally, the external notification server includes one or more of an alarm platform server, an email sending server, and an SMS sending server.

[0028] Secondly, embodiments of this application also provide a data center task notification processing device, applied to the master node server in a task notification processing system, wherein the device is used to implement any of the methods described above.

[0029] Thirdly, embodiments of this application also provide a task notification processing system, the system including a master node server and a slave node server;

[0030] The master node server is used to receive data center task notifications from the data center where the master node server is located, and to receive data center task notifications from the data center where the slave node server is located. The master node server then aggregates and processes the received data center task notifications and sends the aggregated data center task notifications out through an external notification server connected to the master node server.

[0031] The slave node server is used to receive data center task notifications from the data center where the slave node server is located, and send the received data center task notifications to the master node server.

[0032] Optionally, the slave node server is configured to send a node status probe request to the master node server and receive the response result of the master node server to the node status probe request. When it is determined that the current master node server is faulty based on the response result, a new master node server is determined through an election algorithm.

[0033] Fourthly, embodiments of this application also provide an electronic device, including:

[0034] Processor; and

[0035] A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform any of the methods described above.

[0036] Fifthly, embodiments of this application also provide a computer-readable storage medium that stores one or more programs, which, when executed by an electronic device including multiple applications, cause the electronic device to perform any of the methods described above.

[0037] The above-mentioned at least one technical solution adopted in the embodiments of this application can achieve the following beneficial effects: The data center task notification processing method of the embodiments of this application can be executed by the master node server in the task notification processing system. The task notification processing system includes multiple node servers, each deployed in a different data center. When processing data center task notifications, it first receives data center task notifications from the data center where the master node server is located and data center task notifications from the data centers where the slave node servers are located. Then, it summarizes and processes the received data center task notifications. Finally, it sends the summarized data center task notifications out through an external notification server connected to the master node server. The embodiments of this application, by having the master node server in the task notification processing system uniformly summarize and process the data center task notifications received by other node servers before sending them to the corresponding external notification servers, greatly reduce the amount of data center task notifications sent, avoid frequent disturbances to the external notification servers, and facilitate manual viewing of the summarized data center task notifications, eliminating the need for manual viewing on each node server, reducing manual maintenance costs and improving maintenance efficiency. Attached Figure Description

[0038] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0039] Figure 1 This is a schematic diagram of a data center task notification processing flow in the prior art;

[0040] Figure 2 This is a schematic diagram of the structure of a task notification processing system according to an embodiment of this application;

[0041] Figure 3 This is a schematic diagram of the task notification processing flow of a task notification processing system according to an embodiment of this application;

[0042] Figure 4 This is a flowchart illustrating a data center task notification processing method according to an embodiment of this application;

[0043] Figure 5 This is a schematic diagram of the structure of a computer room task notification processing device according to an embodiment of this application;

[0044] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0046] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0047] For ease of understanding of the various embodiments of this application, such as Figure 1 The diagram illustrates a data center task notification processing flow in the prior art. In a distributed system architecture, data is typically distributed across multiple data centers for processing. Figure 1 Taking the six data centers in the example, each data center has a corresponding application (APP) for sending task notifications within that data center. After each data center completes its own task processing, the APP used to send the task notification will call the API interface of that data center to send the task notification to the node server of that data center. Then, the node server of that data center will send the task notification (notify) to the external notification server corresponding to that data center, such as the alarm platform server (Alarm) or the email sending server (MailServer).

[0048] However, the above-mentioned method for handling data center task notifications has the following problems:

[0049] 1) Excessive notification volume leads to overly frequent notifications. Each data center sends a task notification at the scheduled time for each task. If a notification is sent every hour or even every half hour, the number of notifications from 6 data centers will be 6 times the normal volume.

[0050] 2) It cannot effectively show whether all tasks in the data center have been executed successfully, because the task notifications from each data center are scattered in each data center, requiring manual inspection one by one, which is time-consuming and labor-intensive.

[0051] Based on this, embodiments of this application provide a task notification processing system, such as... Figure 2 As shown, a schematic diagram of the structure of a task notification processing system according to an embodiment of this application is provided. The task notification processing system according to this embodiment of the application includes a master node server and a follower node server. It can be seen that there is only one master node, and all other node servers are followers.

[0052] like Figure 3The diagram illustrates a task notification processing flow of a task notification processing system according to an embodiment of this application. In this embodiment, each data center receives notifications sent by the task notification application (APP) within its local data center via an API (Application Programming Interface). The master node server primarily receives task notifications from its own data center and from the data centers of its slave nodes. It then aggregates and processes these notifications, sending the aggregated notifications out through an external notification server connected to the master node server's local data center (IDC), such as an alarm platform server or a mail server. The slave node servers primarily receive task notifications from their own data centers and forward them to the master node server for further aggregation and processing.

[0053] The task notification processing system provided in this application embodiment aggregates and processes the data center task notifications received by other node servers through the master node server in the task notification processing system before sending them to the corresponding external notification server. This greatly reduces the amount of data center task notifications sent and avoids frequent disturbances to the external notification server. At the same time, the aggregated data center task notifications are also easy to view manually without having to view them separately on each node server, which reduces manual operation and maintenance costs and improves operation and maintenance efficiency.

[0054] Furthermore, for applications that send task notifications, there is no need to change the existing sending logic; that is, task notifications can still be sent to the node servers of this IDC. Therefore, the changes to the overall system architecture in this application embodiment are minimal.

[0055] In one embodiment of this application, the slave node server can also be used to send node status probe requests to the master node server to detect the liveness status of the master node server, and, if it is determined that the current master node server has failed, to determine a new master node server through an election algorithm. The specific probe frequency can be flexibly set by those skilled in the art according to actual needs, and is not specifically limited here.

[0056] This application embodiment also provides a data center task notification processing method, executed by the master node server of a task notification processing system, wherein each node server of the task notification processing system is deployed in a different data center, such as... Figure 4 The diagram shows a flowchart of a data center task notification processing method according to an embodiment of this application. The method includes at least the following steps S410 to S440:

[0057] Step S410: Receive the data center task notification from the data center where the master node server is located.

[0058] As described above, the task notification processing system may specifically include multiple node servers distributed in multiple computer rooms. Therefore, the task notification processing system can be regarded as a server cluster. When the entire server cluster starts, a master node server will be determined among the multiple node servers. The computer room task notification processing method of this application embodiment can be executed by the master node server.

[0059] When processing data center task notifications, you can first receive data center task notifications from the data center where the master node server is located. These data center task notifications can be understood as notifications explaining the task execution results of each data center. In practical applications, the task execution result of a data center may be successful or unsuccessful. For unsuccessful tasks, subsequent troubleshooting and other maintenance work is required.

[0060] Step S420: Receive the data center task notification sent by the slave node server from the data center where the slave node server is located.

[0061] For the master node server, in addition to receiving data center task notifications from its own data center, it is also responsible for receiving data center task notifications from each slave node server from its respective data center. In other words, each slave node server forwards all received data center task notifications to the master node server for processing, rather than directly forwarding them to its corresponding external notification server. This reduces the amount of data center task notifications received by the external notification server and avoids frequent disruptions to it.

[0062] It should be noted that there is no strict order between steps S420 and S410. You can receive the data center task notification from the data center where the master node server is located first, or you can receive the data center task notification from the data center where the slave node server is located first, or you can receive them at the same time. No specific restrictions are made here.

[0063] Step S430: Summarize and process the received task notifications from each computer room.

[0064] After receiving data center task notifications from both the data center where the master node server is located and the data center where the slave node servers are located, the master node server needs to summarize and process these data center task notifications so that relevant personnel can view them uniformly later.

[0065] Step S440: Send out the aggregated and processed data center task notification through the external notification server connected to the master node server.

[0066] After the master node server aggregates and processes the task notifications from each data center, it can send the aggregated data center task notifications to the external notification server it is connected to. This ensures that all data center task notifications are processed, and also ensures that only one aggregated data center task notification is sent to the external notification server after a task is completed, avoiding frequent interruptions to the external notification server and facilitating subsequent manual review.

[0067] In this embodiment of the application, the master node server in the task notification processing system uniformly summarizes and processes the data center task notifications received by other node servers before sending them to the corresponding external notification server. This greatly reduces the amount of data center task notifications sent and avoids frequent disturbances to the external notification server. At the same time, the summarized data center task notifications are also easy to view manually without having to view them separately on each node server, which reduces manual operation and maintenance costs and improves operation and maintenance efficiency.

[0068] In one embodiment of this application, the data center task notification received by each node server is received by the application that sent the notification calling the API interface of the local data center. That is, similar to the existing logic, after each data center has finished processing its own task, the application that sent the task notification will send the task notification to the node server of the local data center by calling the API interface of the local data center, without the need to call the API interface across data centers.

[0069] from Figure 2 As can be seen, in real-world application scenarios, a data center typically deploys multiple node servers. When an application sending data center task notifications calls the API interface of its own data center, it does not need to identify which specific node server in the data center the data center task notification should be sent to. In other words, the API interface exposed to the application can be stateless. The multiple node servers within the data center can determine which one is currently receiving the data center task notification through load balancing strategies. That is, at any given time, only one node server in each data center can be used to receive data center task notifications.

[0070] In one embodiment of this application, the master node server is determined from the node servers of the task notification processing system through an election algorithm, and each slave node server stores the node information of the master node server sent based on the Gossip protocol; receiving the data center task notification sent by the slave node server includes: receiving the data center task notification sent by each slave node server based on the stored node information of the master node server.

[0071] As mentioned earlier, the task notification processing system determines a master node server from among multiple node servers upon startup. This master node server then handles the aggregation and sending of task notifications. The determination of the master node server can be achieved using existing election algorithms. This application embodiment provides a master node server election process:

[0072] 1) Each node server issues a vote: Since this is the initial situation, each node server will vote as the leader. Each vote will include the identification information of the nominated node server, and then each will send this vote to other node servers in the cluster.

[0073] 2) Receive votes from each node server: After receiving a vote, each node server in the cluster first determines the validity of the vote, such as checking whether it is a vote in this round.

[0074] 3) Handling votes: For each vote, each node server needs to compare the votes of other node servers with its own vote.

[0075] 4) Voting statistics: After each vote, each node server will count the voting information and determine whether more than half of the node servers have received the same voting information. If so, it is considered that a leader has been elected.

[0076] 5) Change the node server status: Once the leader is determined, each node server will update its own status. For example, if it is a follower, the node server status will change to following, and if it is a leader, the node server status will change to leading.

[0077] Of course, in addition to the election algorithms listed above, those skilled in the art can also use other election algorithms, such as the Raft election algorithm, according to actual needs, without making specific limitations here.

[0078] After the master node server is determined, in order for each slave node server to send the data center task notifications it receives to the master node server for centralized processing, the node information of the master node server, such as the master node server's identifier or IP address, can be synchronously sent to each slave node server.

[0079] The above process can be implemented using the Gossip protocol. The Gossip protocol is a protocol for information exchange between nodes or processes based on the propagation of epidemics. It is widely used in distributed systems. The Gossip protocol uses a random method to spread information to the entire network and makes the data of all nodes in the system consistent within a certain period of time. In this embodiment of the application, it is mainly used to spread the node information of the determined master node server to each slave node server.

[0080] In one embodiment of this application, the method further includes: responding to the node status probe request of the slave node server via the Gossip protocol, so that when each slave node determines that the current master node server is faulty based on the response result of the node status probe request, it determines a new master node server through an election algorithm.

[0081] In real-world applications, the master node server may fail. To avoid impacting task notification processing, probe packets from the Gossip protocol deployed on slave node servers can be used to detect the master node server's liveness. In other words, this embodiment can respond to node status detection requests from slave node servers, allowing each slave node server to detect the current status of the master node server through probe packets in the Gossip protocol. When a failure is detected in the master node server, an election algorithm is used to re-determine the master node server, thus avoiding impact on task notification processing and ensuring business continuity.

[0082] The node status probe request here can be understood as various communication commands. For example, a slave node server can send a Ping command to the master node server, and then receive the return value from the master node server. The node status of the master node server can then be determined based on the return value.

[0083] In one embodiment of this application, the step of summarizing the received task notifications from each data center includes: calling the interface of the data storage module connected to the master node server to store the task notifications from each data center in the data storage module, so as to realize the summarization of the task notifications from each data center through the data storage module.

[0084] In this embodiment of the application, when the master node server aggregates and processes task notifications from various data centers, it can first call the interface of the data storage module connected to the master node server, and then store the task notifications from each data center into the database storage module. This allows for the aggregation and processing of the data center task notifications within the data storage module. The data storage module can be a Redis database or Zookeeper. Of course, those skilled in the art can flexibly configure the storage method for the data center task notifications according to actual needs, and no specific limitations are imposed here.

[0085] In one embodiment of this application, storing each data center task notification in the data storage module includes: determining the identification information of the data center task notification; determining whether a data center task notification corresponding to the identification information of the data center task notification already exists in the data storage module; if it exists, then the data center task notification is not stored in the data storage module; if it does not exist, then the data center task notification is stored in the data storage module.

[0086] In real-world applications, data centers may experience multiple task failures due to equipment malfunctions or other anomalies during task execution. This can result in receiving multiple duplicate data center task notifications for the same task. To address this, this embodiment of the application can perform deduplication or filtering on data center task notifications when storing them in the data storage module. This avoids data redundancy and facilitates subsequent viewing and processing by relevant personnel.

[0087] Specifically, each data center task notification carries its own identification information, such as the task execution time batch, task notification name, and task execution result. The task execution time batch can be understood as the time batch during which the data center should execute tasks, the task notification name can be understood as the name of the specific task to be executed, and the task execution result (result) is the result of whether the data center successfully or failed to execute the task. The following is a data storage structure for data center task notifications:

[0088] Key: Task Execution Time Batch - Task Notification Name

[0089] Value: list:

[0090] IDC-1-result

[0091] IDC-2-result

[0092] …

[0093] Based on the above identification information, a search and matching process can be performed in the data storage module to determine whether the data center task notification has already been stored. If it has already been stored, it will not be stored again. If it has not been stored, the relevant information of the data center task notification can be directly stored in the data storage module.

[0094] For example, suppose the currently received data center task notification corresponds to the batch with the task execution time of 11:00, the task notification name is transaction reconciliation, and the task execution result is execution failure. If the data storage module has already recorded a piece of information that is exactly the same as the above data center task notification, it will not be stored again.

[0095] In real-world applications, the following situations may occur: When executing a task, network interruptions or other abnormalities may cause the task to temporarily fail, triggering a task failure notification. When the task is retried through the retry mechanism, the task may succeed due to network recovery, triggering a task success notification. In this case, the execution of the same task in the same time batch will produce two different execution results. One approach is to store both results in the data storage module, while another approach is to remove the previously failed record and only retain the last successful record.

[0096] It should be noted that the task execution results carried in the data center task notification, such as whether the task was successfully executed or failed, can indicate to some extent whether there is an abnormal situation in the data center. In addition, when the master node server receives data center task notifications from other slave node servers, it can also determine whether there is an abnormal state in the data center where the other slave node services are located by using a pre-set timeout.

[0097] For example, suppose there are six data centers: IDC1, IDC2, ..., IDC6. Node server 'a' in IDC1 is the current master node server, with a timeout of 10 minutes. When node server 'a' receives data center task notifications from slave node servers in the other five IDCs, it will wait for 10 minutes. If it only receives data center task notifications from slave node servers in IDC2-IDC5 within 10 minutes, but does not receive data center task notifications from slave node server in IDC6, it indicates that slave node server in IDC6 may have malfunctioned. Such an anomaly can also be recorded when summarizing data center task notifications.

[0098] In one embodiment of this application, the step of summarizing the received task notifications from each data center further includes: determining the type of each data center task notification; and summarizing the task notifications from each data center according to their type.

[0099] In this embodiment of the application, when summarizing and processing data center task notifications, the type of data center task notification can be determined first, and then each data center task notification can be summarized and processed separately according to its type, which is convenient for subsequent manual viewing.

[0100] Specifically, as mentioned earlier, the data center task notification will carry a task notification name, which indicates which type of specific task the data center is processing. Therefore, the type of data center task notification is determined based on the task notification name.

[0101] In one embodiment of this application, the external notification server includes one or more of an alarm platform server, an email sending server, and an SMS sending server.

[0102] In this embodiment of the application, after the master node server summarizes and processes the task notifications from each data center, it can send the summarized data center task notifications to the external notification server corresponding to the data center where the master node server is located. This allows the external notification server to promptly remind relevant personnel to perform subsequent operation and maintenance, saving operation and maintenance time and improving operation and maintenance efficiency.

[0103] The external notification server here can be any server with message notification capabilities, such as an alarm platform server, email server, or SMS server. After receiving the aggregated and processed data center task notifications, the alarm platform server will issue alarms for any task execution failures mentioned in the notifications, enabling relevant personnel to address the issues promptly. The email and SMS servers will directly send the aggregated and processed data center task notifications to relevant personnel for viewing and processing.

[0104] This application embodiment also provides a data center task notification processing device 500, applied to the master node server in a task notification processing system, such as... Figure 5 The diagram shows a structural schematic of a data center task notification processing device according to an embodiment of this application. The device 500 includes: a first receiving unit 510, a second receiving unit 520, a summarizing unit 530, and a sending unit 540, wherein:

[0105] The first receiving unit 510 is used to receive data center task notifications from the data center where the master node server is located.

[0106] The second receiving unit 520 is used to receive the data center task notification sent by the slave node server from the data center where the slave node server is located.

[0107] The aggregation unit 530 is used to aggregate and process the received task notifications from various computer rooms.

[0108] The sending unit 540 is used to send out the aggregated and processed data center task notification through an external notification server connected to the master node server.

[0109] In one embodiment of this application, the master node server is determined from the node servers of the task notification processing system through an election algorithm, and each slave node server stores the node information of the master node server sent based on the Gossip protocol; the second receiving unit 520 is specifically used to: receive the data center task notification sent by each slave node server based on the stored node information of the master node server.

[0110] In one embodiment of this application, the apparatus further includes: a response unit, configured to respond to a node status probe request from a slave node server via the Gossip protocol, so that when each slave node determines that the current master node server is faulty based on the response result of the node status probe request, it can determine a new master node server through an election algorithm.

[0111] In one embodiment of this application, the aggregation unit 530 is specifically used to: call the interface of the data storage module connected to the master node server, and store the task notifications of each computer room into the data storage module, so as to realize the aggregation of the task notifications of each computer room through the data storage module.

[0112] In one embodiment of this application, the aggregation unit 530 is specifically used to: determine the identification information of the data center task notification; determine whether a data center task notification corresponding to the identification information of the data center task notification already exists in the data storage module; if it exists, then the data center task notification is not stored in the data storage module; if it does not exist, then the data center task notification is stored in the data storage module.

[0113] In one embodiment of this application, the aggregation unit 530 is specifically used to: determine the type of task notification for each computer room; and aggregate the task notifications for each computer room according to their type.

[0114] In one embodiment of this application, the aggregated data center task notification includes one or more of the following: task execution time batch, task notification name, and task execution result.

[0115] In one embodiment of this application, the external notification server includes one or more of an alarm platform server, an email sending server, and an SMS sending server.

[0116] It is understood that the above-mentioned data center task notification processing device can implement each step of the data center task notification processing method executed by the clearing server in the foregoing embodiments. The relevant explanations of the data center task notification processing method are applicable to the data center task notification processing device, and will not be repeated here.

[0117] Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Please refer to it. Figure 6At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and memory. The memory may include main memory, such as high-speed random-access memory (RAM), or non-volatile memory, such as at least one disk drive. Of course, the electronic device may also include other hardware required for other business operations.

[0118] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0119] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0120] The processor reads the corresponding computer program from non-volatile memory into main memory and then executes it, forming a data center task notification processing device at the logical level. The processor executes the program stored in memory and specifically performs the following operations:

[0121] Receive data center task notifications from the data center where the master node server is located;

[0122] Receive data center task notifications from the slave node server regarding the data center where the slave node server is located;

[0123] The received task notifications from each computer room are aggregated and processed.

[0124] The aggregated and processed data center task notifications are sent out through the external notification server connected to the master node server.

[0125] The above is as stated in this application. Figure 4The method executed by the data center task notification processing device disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0126] The electronic device can also perform Figure 4 The method for executing the task notification processing device in the computer room, and the implementation of the task notification processing device in the computer room Figure 4 The functions of the embodiments shown are not described in detail here.

[0127] This application also proposes a computer-readable storage medium that stores one or more programs, the programs including instructions that, when executed by an electronic device including multiple applications, enable the electronic device to perform... Figure 4 The method executed by the computer room task notification processing device in the illustrated embodiment is specifically used to perform the following:

[0128] Receive data center task notifications from the data center where the master node server is located;

[0129] Receive data center task notifications from the slave node server regarding the data center where the slave node server is located;

[0130] The received task notifications from each computer room are aggregated and processed.

[0131] The aggregated and processed data center task notifications are sent out through the external notification server connected to the master node server.

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

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

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

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

[0136] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0137] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0138] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0139] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

[0141] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for processing task notifications in a computer room, executed by the master node server in a task notification processing system, wherein, The task notification processing system has its node servers deployed in various data centers, and the method includes: Receive data center task notifications from the data center where the master node server is located; Receive data center task notifications from the slave node server regarding the data center where the slave node server is located; The received task notifications from each computer room are aggregated and processed. The aggregated and processed data center task notifications are sent out through the external notification server connected to the master node server. The process of aggregating and processing the received task notifications from various computer rooms includes: The interface of the data storage module connected to the master node server is called to store the task notifications of each computer room into the data storage module, so as to realize the aggregation of task notifications of each computer room through the data storage module; The step of storing task notifications from each computer room into the data storage module also includes: The identification information of the data center task notification is determined, which includes the task execution time batch, task notification name, and task execution result corresponding to the data center task notification. If two different task execution results are generated when the same task is executed in the same batch at the same time, both different task execution results are stored in the data storage module, or the previous task execution result is removed and only the last task execution result is retained; The method further includes: The system responds to node status probe requests from slave nodes via the Gossip protocol, enabling each slave node to determine a new master node server through an election algorithm when it determines that the current master node server has failed based on the response to the node status probe request. The step of storing task notifications from each computer room into the data storage module includes: Determine whether a data storage module already contains a data center task notification corresponding to the identifier information of the data center task notification; If it exists, the data center task notification will not be stored in the data storage module; If it does not exist, the data center task notification will be stored in the data storage module. The method further includes: When receiving a data center task notification from the slave node server, the system determines whether the data center where the slave node server is located is in an abnormal state by using a preset timeout period, and obtains the result of the abnormal state determination. When summarizing and processing the received task notifications from each computer room, the determination results of the abnormal status are also recorded.

2. The method as described in claim 1, wherein, The master node server is determined from the node servers of the task notification processing system through an election algorithm, and each slave node server stores the node information of the master node server sent based on the Gossip protocol. The receipt of data center task notifications sent from the slave node server includes: Receive data center task notifications sent by each slave node server based on the saved node information of the master node server.

3. The method as described in claim 1, wherein, The process of aggregating and processing the received task notifications from various computer rooms also includes: Determine the type of task notification for each computer room; The task notifications from each computer room are summarized and processed according to their type.

4. The method as described in claim 1, wherein, The aggregated data center task notification includes one or more of the following: task execution time batch, task notification name, and task execution result.

5. A data center task notification processing device, applied to the master node server of a task notification processing system, wherein, The apparatus is used to implement the method described in any one of claims 1 to 4.

6. A task notification processing system, the system comprising a master node server and slave node servers; The master node server is used to receive data center task notifications from the data center where the master node server is located, and to receive data center task notifications from the data center where the slave node server is located. The master node server then aggregates and processes the received data center task notifications and sends the aggregated data center task notifications out through an external notification server connected to the master node server. The slave node server is used to receive data center task notifications from the data center where the slave node server is located, and send the received data center task notifications to the master node server. The master node server is also used for: The interface of the data storage module connected to the master node server is called to store the task notifications of each computer room into the data storage module, so as to realize the aggregation of task notifications of each computer room through the data storage module; The master node server is also used for: The identification information of the data center task notification is determined, which includes the task execution time batch, task notification name, and task execution result corresponding to the data center task notification. If two different task execution results are generated when the same task is executed in the same batch at the same time, both different task execution results are stored in the data storage module, or the previous task execution result is removed and only the last task execution result is retained; The master node server is also used for: The system responds to node status probe requests from slave nodes via the Gossip protocol, enabling each slave node to determine a new master node server through an election algorithm when it determines that the current master node server has failed based on the response to the node status probe request. The master node server is also used for: Determine whether a data storage module already contains a data center task notification corresponding to the identifier information of the data center task notification; If it exists, the data center task notification will not be stored in the data storage module; If it does not exist, the data center task notification will be stored in the data storage module. The master node server is also used for: When receiving a data center task notification from the slave node server, the system determines whether the data center where the slave node server is located is in an abnormal state by using a preset timeout period, and obtains the result of the abnormal state determination. When summarizing and processing the received task notifications from each computer room, the determination results of the abnormal status are also recorded.

7. The system of claim 6, wherein, The slave node server is used to send a node status probe request to the master node server and receive the response result of the master node server to the node status probe request. When it is determined that the current master node server is faulty based on the response result, a new master node server is determined through an election algorithm.

Images