Emergency processing method, device and equipment for persistent data registration center

Abstract

The embodiment of the invention relates to the technical field of communication, in particular to an emergency processing method, device and equipment for a persistent data registration center. According to the scheme, service registration or continuation is carried out by acquiring the service registration information of at least two random node providers in the registration center, and meanwhile, the self-service portal periodically acquires the full-quantity provider service registration information of the registration center and the timestamp of the full-quantity provider service registration information for persistent storage; then, the monitoring center monitors and judges whether the registration center operates normally in real time, and if any registration center node crashes or has a network fault, connection with the emergency center is established; and the emergency center loads full-quantity provider service registration information when the fault occurs according to the timestamp and the snapshot file, and replaces the registration center to perform external service on the service gateway or the application. Therefore, persistence of registration data of the registration center is achieved, meanwhile, the registration center real-time data monitoring and fault sensing capacity is achieved, and the registration data recovery capacity of a single micro-service level is provided.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of data processing, and in particular to an emergency processing method, device and equipment for a persistent data registration center. Background Art

[0002] The registration center is the "address book" in the microservice architecture, which records the mapping relationship between services and service addresses. In a distributed microservice architecture, a registration center cluster often contains multiple nodes. The microservice provider system will randomly register with the registration center node, and the registration center nodes will synchronize the provider information to ensure data consistency among the cluster nodes. The consumer system that accesses the provider periodically and randomly accesses the registration center node for service discovery and updates the service discovery results to the local cache. The consumer system obtains the provider address from the local cache and directly connects to the corresponding provider to achieve point-to-point communication or gateway communication. The existing solution does not have an emergency module design for the scenario of node data disorder. The data consistency of the existing registration center is heavily dependent on the network connectivity of the environment. When intermittent network problems or failures occur in the environment, data synchronization between the nodes of the registration center may fail due to communication problems, and the registration information of some or all nodes in the cluster will be missing. When the registration center node with missing registration information for the consumer direction performs service discovery, the call may fail because the corresponding provider address cannot be obtained.

[0003] Currently, there is an urgent need for an emergency response method for a persistent data registration center, so as to realize different forms of automatic registration center failure recovery and solve the problem that the existing solution only supports manual failure recovery. Summary of the invention

[0004] In order to solve the problem in the prior art that when intermittent network problems or failures occur in the environment, the data synchronization between the nodes of the registration center may fail due to communication problems, the embodiments of this specification provide an emergency processing method, device and equipment for a persistent data registration center, which realizes the persistence of the registration data of the registration center by performing heartbeat detection on the registration center module, and enables the emergency center to take over all external interfaces of the registration center, and has the emergency capability to replace all functions of the registration center. At the same time, the emergency center has the automatic switching mode of real-time data monitoring and fault perception capabilities of the registration center, and provides single microservice-level registration data recovery capabilities.

[0005] The specific technical solutions of the embodiments of this specification are as follows:

[0006] On the one hand, an embodiment of the present specification provides an emergency handling method for a persistent data registration center, the method comprising: a service gateway or an application connects a registration center and an emergency center, and a self-service portal and a monitoring center are also connected between the registration center and the emergency center;

[0007] Obtaining provider service registration information, randomly selecting any node in the registration center for service registration or renewal, and synchronizing the provider service registration information to at least two random nodes in the registration center;

[0008] Selecting a node randomly selects a node in the registration center to provide external services to the service gateway or application;

[0009] The self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the registration center for persistent storage;

[0010] The monitoring center monitors each node in the registration center in real time. If it is determined that the data of any node is unavailable, the failure time is recorded and a connection is established between the service gateway and the emergency center.

[0011] The emergency center matches the fault time and the timestamp in the self-service portal, loads the full provider service registration information corresponding to the fault time, and replaces the registration center to provide external services to the service gateway or application.

[0012] Furthermore, the monitoring center monitors each node in the registration center in real time and further includes:

[0013] The real-time monitoring includes performing heartbeat detection on each node in the registration center, real-time detection of the number of service gateways or applications and error log alarms, and determining whether the registration center node data is available.

[0014] Loading the full amount of provider service registration information corresponding to the failure time further includes:

[0015] The external service of the emergency center includes restoring the full amount of provider service registration information corresponding to the failure time;

[0016] If some microservices or gateways have data changes after the failure time, the self-service portal dynamically modifies and issues the data changes according to the full provider service registration information after the failure time.

[0017] Furthermore, replacing the registration center to provide external services to the service gateway or application further includes:

[0018] The self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the emergency center for persistent storage;

[0019] If the monitoring center detects that the registration center has returned to normal, the registration center will resume providing external services to the service gateway or application.

[0020] Furthermore, the self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the registration center, further including:

[0021] The self-service portal obtains snapshot files of all nodes in the registration center according to a predetermined period as the full provider service registration information.

[0022] Furthermore, the snapshot file includes: microservice name, instance id, registration information: provider ip port, instance status.

[0023] On the other hand, the embodiment of this specification also provides an emergency processing device of a persistent data registration center, the device comprising:

[0024] An information acquisition module, used to acquire provider service registration information, randomly select any node in the registration center for service registration or renewal, and synchronize the provider service registration information to at least two random nodes in the registration center;

[0025] A registration center module is used to randomly select nodes to provide external services to the service gateway or application;

[0026] A self-service portal module is used to periodically obtain the full amount of provider service registration information and its timestamp in the registration center for persistent storage;

[0027] A monitoring center module, used to monitor each node in the registration center in real time. If it is determined that the data of any registration center node is unavailable, the failure time is recorded and the service gateway is connected to the emergency center;

[0028] The emergency center module is used to match the fault time and the timestamp in the self-service portal, load the full provider service registration information corresponding to the fault time, and replace the registration center to provide external services to the service gateway or application.

[0029] On the other hand, an embodiment of the present specification further provides a computer device, including a memory, a processor, and a computer program stored in the memory, and the processor implements the above method when executing the computer program.

[0030] On the other hand, an embodiment of the present specification further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0031] Finally, the embodiments of this specification also provide a computer program product, wherein the computer program product includes a computer program, and the computer program implements the above method when executed by a processor.

[0032] Using the embodiments of this specification, a design of an emergency center based on persistent data is provided. This solution connects the registration center and the emergency center through a service gateway or application. At the same time, the registration center and the emergency center are also connected with a self-service portal and a monitoring center. By obtaining the provider service registration information, any node in the registration center is randomly selected for service registration or renewal, and the provider service registration information is synchronized to at least two random nodes in the registration center. The nodes in the registration center provide external services to the service gateway or application; at the same time, the self-service portal regularly obtains the full provider service registration information and its timestamp in the registration center for persistent storage to ensure that the full provider service registration information at any time point can be obtained at any time; the monitoring center monitors each node in the registration center in real time to ensure that it can be discovered in time when a problem occurs in the registration center node. If it is determined that the data of any registration center node is unavailable and a downtime or network failure occurs, the failure time is recorded and the service gateway is connected to the emergency center; the emergency center obtains the failure time of the last heartbeat detection before the network failure, and matches it in the self-service portal according to the failure time and timestamp, loads the full provider service registration information corresponding to the failure time, and uses the emergency center to replace the registration center to provide external services to the service gateway or application. This enables the persistence of the registration data of the registration center, ensuring that the emergency center can take over all external interfaces, and has the above-mentioned features of the overall emergency center solution. At the same time, the emergency center has the ability to monitor the real-time data of the registration center and detect faults, and provides single microservice-level registration data recovery capabilities. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0034] Figure 1 It is a schematic diagram of an implementation system of an emergency processing method of a persistent data registration center in an embodiment of this specification;

[0035] Figure 2 The figure is a flow chart of an emergency processing method of a persistent data registration center in an embodiment of this specification;

[0036] Figure 3The figure is a schematic diagram of the process of loading the full amount of provider service registration information corresponding to the fault time in the embodiment of this specification;

[0037] Figure 4 The figure is a schematic diagram of a process of replacing the registration center to provide external services to the service gateway or application in an embodiment of this specification;

[0038] Figure 5 The figure is a schematic diagram of the structure of the emergency processing system of the persistent data registration center of this embodiment;

[0039] Figure 6 The figure shows a schematic diagram of the structure of the emergency processing device of the persistent data registration center of this embodiment;

[0040] Figure 7 The figure is a schematic diagram of the structure of a computer device in an embodiment of the present specification.

[0041]

Description of reference numerals

[0042] 101. Service gateway or application;

[0043] 102. Registration center;

[0044] 103. Emergency Center;

[0045] 601, information acquisition module;

[0046] 602. Registration center module;

[0047] 603. Self-service portal module;

[0048] 604, monitoring center module;

[0049] 605, emergency center module;

[0050] 702. Computer equipment;

[0051] 704. Processing equipment;

[0052] 706. Storage resources;

[0053] 708. Drive system;

[0054] 710, input / output module;

[0055] 712. Input devices;

[0056] 714. Output devices;

[0057] 716. Presentation equipment;

[0058] 718. Graphical user interface;

[0059] 720, network interface;

[0060] 722. Communication link;

[0061] 724. Communication bus. DETAILED DESCRIPTION

[0062] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on the embodiments in the embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the embodiments of this specification.

[0063] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.

[0064] It should be noted that the acquisition, storage, use, and processing of data in the technical solutions of the embodiments of this specification comply with the relevant provisions of national laws and regulations.

[0065] It should be noted that in the embodiments of this specification, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of this application, but it does not mean that the applicant has or will necessarily use the solution.

[0066] like Figure 1The diagram of the implementation system of the emergency handling method of a persistent data registration center in the embodiment of the present specification is shown, including a service gateway or application 101, a registration center 102 and an emergency center 103. The service gateway or application 101, the registration center 102 and the emergency center 103 can communicate through a network, and the network can include a local area network (Local Area Network, referred to as LAN), a wide area network (Wide Area Network, referred to as WAN), the Internet or a combination thereof, and is connected to a website, a user device (such as a computing device) and a back-end system. Optionally, the registration center 102 can be a node of a cloud computing system, or each server can be a separate cloud computing system, including multiple computers interconnected by a network and working as a distributed processing system.

[0067] The full provider service registration information is obtained and sent to the registration center 102. The registration center 102 creates a data synchronization task based on the full provider service registration information and sends it to at least two different registration center modules in the registration center for processing. Then, external services are provided through the service gateway or application 101. At the same time, when a downtime or link problem occurs in the registration center 102, the module in the registration center 102 can be replaced by connecting to the emergency center 103 to work.

[0068] In addition, it should be noted that Figure 1 What is shown is only one application environment provided by the embodiment of this specification. In actual application, other application environments may also be included, and this specification does not limit it.

[0069] In view of the problems existing in the prior art, the embodiment of this specification provides an emergency processing method for a persistent data registration center. In the embodiment of this specification, Figure 2 The figure shows a flowchart of the emergency handling method of the persistent data registration center in the embodiment of this specification. This figure describes the emergency handling process of the persistent data registration center. The order of steps listed in the embodiment is only one way of executing the steps among many orders, and does not represent the only execution order. When the actual system or device product is executed, it can be executed in the order of the method shown in the embodiment or the accompanying drawings or in parallel. Specifically, Figure 2 As shown, the method may include: a service gateway or application connects a registration center and an emergency center, wherein a self-service portal and a monitoring center are also connected between the registration center and the emergency center;

[0070] Step 201: Acquire provider service registration information, randomly select any node in the registration center to register or renew the service, and synchronize the provider service registration information to at least two random nodes in the registration center;

[0071] Step 202: Select a node to randomly select a node in the registration center to provide external services to the service gateway or application;

[0072] Step 203: The self-service portal periodically obtains the full provider service registration information and its timestamp in the registration center for persistent storage;

[0073] Step 204: the monitoring center monitors each node in the registration center in real time. If it is determined that the data of any node is unavailable, the failure time is recorded and the service gateway is connected to the emergency center.

[0074] Step 205: The emergency center matches the fault time and the timestamp in the self-service portal, loads the full provider service registration information corresponding to the fault time, and replaces the registration center to provide external services to the service gateway or application.

[0075] Using the embodiments of this specification, a design of an emergency center based on persistent data is provided. This solution connects the registration center and the emergency center through a service gateway or application. At the same time, the registration center and the emergency center are also connected with a self-service portal and a monitoring center. By obtaining the provider service registration information, any node in the registration center is randomly selected for service registration or renewal, and the provider service registration information is synchronized to at least two random nodes in the registration center. The nodes in the registration center provide external services to the service gateway or application; at the same time, the self-service portal regularly obtains the full provider service registration information and its timestamp in the registration center for persistent storage to ensure that the full provider service registration information at any time point can be obtained at any time; the monitoring center monitors each node in the registration center in real time to ensure that it can be discovered in time when a problem occurs in the registration center node. If it is determined that the data of any registration center node is unavailable and a downtime or network failure occurs, the failure time is recorded and the service gateway is connected to the emergency center; the emergency center obtains the failure time of the last heartbeat detection before the network failure, and matches it in the self-service portal according to the failure time and timestamp, loads the full provider service registration information corresponding to the failure time, and uses the emergency center to replace the registration center to provide external services to the service gateway or application. This enables the persistence of the registration data of the registration center, ensuring that the emergency center can take over all external interfaces, and has the above-mentioned features of the overall emergency center solution. At the same time, the emergency center has the ability to monitor the real-time data of the registration center and detect faults, and provides single microservice-level registration data recovery capabilities.

[0076] In the embodiments of the present specification, when the network environment and the registration center node are operating normally, the portal will periodically pull the full provider service registration information from the registration center and save it to the database or other persistent storage with a timestamp. When the environment has intermittent network problems and the registration information of the provider system changes, resulting in data asynchrony between the registration center nodes, for example, an instance of the provider system crashes, but the service caller continues to be unable to perceive the instance crash and continues to send transactions to it, there will be continuous errors, and it is necessary to replace the image and restart the application to enable the emergency center. Then select the snapshot according to the timestamp, and switch the registration center module to the corresponding emergency module. Before providing external services, the emergency module requests the portal to pull the full provider service information at the corresponding time point and put it into the local cache.

[0077] In the embodiment of this specification, in order to obtain the status of each node in the registration center in time and ensure that the fault can be discovered as soon as possible when a network fault or downtime occurs, the monitoring center monitors each node in the registration center in real time and further includes:

[0078] The real-time monitoring includes performing heartbeat detection on each node in the registration center, real-time detection of the number of service gateways or applications and error log alarms, and determining whether the registration center node data is available.

[0079] Specifically, the system is in snapshot mode during operation, and the emergency center cannot perceive changes in the background address and other related information. When the background instance is restarted or a new instance is expanded, it will go to the registration center to register. Therefore, when the real-time changes in the provider registration information are obvious on the monitoring registration center, such as a significant decrease, it can be determined that the network has a fault. At the same time, according to different business needs, the registration center monitoring center will also set different thresholds. When the node with the problem reaches the threshold, the fault time will be recorded and the service gateway will be connected to the emergency center.

[0080] In the embodiments of this specification, in order to minimize data loss, Figure 3 As shown, loading the full provider service registration information corresponding to the failure time further includes:

[0081] Step 301: the emergency center's external service includes restoring the full amount of provider service registration information corresponding to the fault time;

[0082] Step 302: If some microservices or gateways have data changes after the failure time, the self-service portal dynamically modifies and issues the data changes according to the full provider service registration information after the failure time.

[0083] Specifically, between the time when the monitoring center discovers the fault and records the fault time and the time when the emergency center completely replaces the registration center to provide external services, there may still be data updates or changes in the registration center. Therefore, in order to avoid the loss of data changes during this period, after the emergency center loads the full provider service registration information corresponding to the fault time, the self-service portal will also confirm whether there are any data changes after the fault time based on the full provider service registration information stored after the fault time. If there are any data changes, the self-service portal will dynamically modify and issue them based on the data changes recorded in the full provider service registration information.

[0084] In the embodiment of this specification, in order to ensure that the registration center can resume normal work after the network returns to normal, such as Figure 4 As shown, replacing the registration center to provide external services to the service gateway or application further includes:

[0085] Step 401: the self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the emergency center for persistent storage;

[0086] Step 402: If the monitoring center detects that the registration center has returned to normal, the registration center will be restored to provide external services to the service gateway or application.

[0087] In the embodiment of the present specification, in order to obtain the full provider service registration information, the self-service portal periodically obtains the full provider service registration information and its timestamp in the registration center, further comprising:

[0088] The self-service portal obtains snapshot files of all nodes in the registration center according to a predetermined period as the full provider service registration information.

[0089] Furthermore, the snapshot file includes: microservice name, instance id, registration information: provider ip port, instance status.

[0090] In another embodiment of the present specification, when a new provider instance needs to be connected or the information of the existing provider instance changes during the operation of the emergency center, the information change of the first j node will be detected, and a data synchronization task will be created to synchronize the content of the information change to the second node, thereby realizing information synchronization in at least two nodes. At the same time, the registration data of the registration center can be monitored in real time through the monitoring platform, and customized water levels can be configured according to different business capability recovery requirements to ensure that the startup of the emergency center can be automatically triggered.

[0091] In another embodiment of the present specification, the emergency module can provide all external interfaces connected to the registration center. Because the cluster nodes pull the same full provider service information, the data consistency between the nodes can be guaranteed. In the embodiment of the present specification, the problem that the existing solution cannot avoid the node data confusion due to data synchronization failure in extreme scenarios is solved. The emergency module can not only perform the functions of the registration center but also remove the complex mechanism related to the registration center data synchronization. Each node loads the same static data when it starts, thereby ensuring the consistency of the data of each node. The persistence of the registration data of the registration center is realized, and the full external interface takeover of the registration center is realized. The overall solution of the emergency center has the above characteristics. At the same time, it has an automatic switching mode of the emergency center with the ability to monitor the real-time data of the registration center and perceive faults. During the takeover of the emergency module, it can also provide single microservice-level registration data recovery capabilities.

[0092] In one embodiment of this specification, Figure 5 As shown in the figure, when the network environment and the registration center node are operating normally, the portal will periodically pull the full provider service registration information from the registration center and save it with the timestamp to the database or other persistent storage. When the environment has intermittent network problems that cause the data between the registration center nodes to be out of sync, the emergency center is enabled to select the fast pull of the full provider service information at the corresponding time point according to the timestamp and put it into the local cache. When a new provider instance needs to be connected or the information of the existing provider instance changes during the operation of the emergency center, it is necessary to notify the operation and maintenance personnel to download the snapshot file of the corresponding timestamp from the portal first, add the new provider information, upload it to the portal and send it to the emergency center, so as to realize the customized single microservice-level registration data recovery capability. At the same time, the registration data of the registration center can be monitored in real time through the monitoring platform, and customized waterlines can be configured according to the recovery requirements of different business capabilities to automatically trigger the start of the emergency center. The emergency center can provide all external interfaces of the registration center. Because the cluster nodes pull the same full provider service information, the data consistency between the nodes can be guaranteed.

[0093] As an example of this specification, please refer to Figure 6 The figure is a schematic diagram of the specific structure of the emergency processing device of the persistent data registration center of this embodiment.

[0094] The information acquisition module 601 is used to acquire the provider service registration information, randomly select any node in the registration center to register or renew the service, and synchronize the provider service registration information to at least two random nodes in the registration center;

[0095] A registration center module 602 is used to randomly select a node to provide external services to the service gateway or application;

[0096] The self-service portal module 603 is used to periodically obtain the full amount of provider service registration information and its timestamp in the registration center for persistent storage;

[0097] The monitoring center module 604 is used to monitor each node in the registration center in real time. If it is determined that the data of any registration center node is unavailable, the failure time is recorded and the service gateway is connected to the emergency center module;

[0098] The emergency center module 605 is used to match the fault time and the timestamp in the self-service portal, load the full provider service registration information corresponding to the fault time, and replace the registration center to provide external services to the service gateway or application.

[0099] Since the principle of solving the problem by the above device is similar to that of the above method, the implementation of the above system can refer to the implementation of the above method, and the repeated parts will not be repeated.

[0100] like Figure 7 The figure is a schematic diagram of the structure of a computer device according to an embodiment of the present specification. The computer device according to the embodiment of the present specification can run the method according to the embodiment of the present specification.

[0101] The computer device 702 may include one or more processing devices 704, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 702 may also include any storage resources 706 for storing any type of information such as code, settings, data, etc. Without limitation, for example, the storage resources 706 may include any one or more combinations of the following: any type of RAM, any type of ROM, a flash memory device, a hard disk, an optical disk, etc. More generally, any storage resource may use any technology to store information.

[0102] Further, any storage resource may provide volatile or non-volatile retention of information.

[0103] Further, any storage resource may represent a fixed or removable component of the computer device 702. In one case, when the processing device 704 executes the associated instructions stored in any storage resource or combination of storage resources, the computer device 702 may perform any operation of the associated instructions. The computer device 702 also includes one or more drive systems 708 for interacting with any storage resource, such as a hard disk drive system, an optical disk drive system, etc.

[0104] The computer device 702 may also include an input / output module 710 (I / O) for receiving various inputs (via input devices 712) and for providing various outputs (via output devices 714). A specific output mechanism may include a presentation device 716 and an associated graphical user interface 718 (GUI). In other embodiments, the input / output module 710 (I / O), input device 712, and output device 714 may not be included, and the computer device 702 may be used as a computer device in a network. The computer device 702 may also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the components described above together.

[0105] The communication link 722 may be implemented in any manner, for example, through a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc. governed by any protocol or combination of protocols.

[0106] The embodiments of the present specification also provide a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program implements the above method when executed by a processor.

[0107] The embodiments of the present specification also provide a computer-readable instruction, wherein when a processor executes the instruction, the program therein causes the processor to execute the above method.

[0108] It should be understood that in the various embodiments of the present specification, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present specification.

[0109] It should also be understood that in the embodiments of this specification, the term "and / or" is only a description of the association relationship of the associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in the embodiments of this specification generally indicates that the associated objects before and after are in an "or" relationship.

[0110] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of this specification can be implemented with electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in terms of function in the above description. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of this specification.

[0111] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0112] In the several embodiments provided in the embodiments of this specification, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or it can be an electrical, mechanical or other form of connection.

[0113] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of this specification.

[0114] In addition, each functional unit in each embodiment of the present specification can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional units.

[0115] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of this specification is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the embodiment of this specification. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, RandomAccess Memory), disk or optical disk and other media that can store program code.

[0116] The embodiments of this specification use specific embodiments to illustrate the principles and implementation methods of the embodiments of this specification. The description of the above embodiments is only used to help understand the methods and core ideas of the embodiments of this specification. At the same time, for those skilled in the art, according to the ideas of the embodiments of this specification, there will be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the embodiments of this specification.

Claims

1. An emergency processing method for a persistent data registration center, characterized in that: The method includes: a service gateway or application connects a registration center and an emergency center, wherein a self-service portal and a monitoring center are connected between the registration center and the emergency center; Obtaining provider service registration information, randomly selecting any node in the registration center for service registration or renewal, and synchronizing the provider service registration information to at least two random nodes in the registration center; Selecting a node randomly selects a node in the registration center to provide external services to the service gateway or application; The self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the registration center for persistent storage; The monitoring center monitors each node in the registration center in real time. If it is determined that the data of any node is unavailable, the failure time is recorded and the service gateway is connected to the emergency center. The emergency center matches the fault time and the timestamp in the self-service portal, loads the full provider service registration information corresponding to the fault time, and replaces the registration center to provide external services to the service gateway or application.

2. The emergency handling method of the persistent data registration center according to claim 1 is characterized in that: The monitoring center further monitors each node in the registration center in real time, The real-time monitoring includes performing heartbeat detection on each node in the registration center, detecting the number of service gateways or applications and error log alarms in real time, and determining whether the node data of the registration center is available.

3. The emergency handling method of the persistent data registration center according to claim 1 is characterized in that: Loading the full amount of provider service registration information corresponding to the failure time further includes: The external service of the emergency center includes restoring the full amount of provider service registration information corresponding to the failure time; If some microservices or gateways have data changes after the failure time, the self-service portal dynamically modifies and issues the data changes according to the full provider service registration information after the failure time.

4. The emergency handling method of the persistent data registration center according to claim 1 is characterized in that: Replacing the registration center to provide external services to the service gateway or application further includes: The self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the emergency center for persistent storage; If the monitoring center detects that the registration center has returned to normal, the registration center will resume providing external services to the service gateway or application.

5. The emergency handling method of the persistent data registration center according to claim 1 is characterized in that: The self-service portal periodically obtains the full amount of provider service registration information and its timestamp in the registration center, further comprising: The self-service portal obtains snapshot files of all nodes in the registration center according to a predetermined period as the full provider service registration information.

6. The emergency handling method of the persistent data registration center according to claim 5 is characterized in that: The snapshot file includes: microservice name, instance id, registration information: provider ip port, instance status.

7. An emergency processing device for a persistent data registration center, characterized in that: The device comprises, An information acquisition module, used to acquire provider service registration information, randomly select any node in the registration center for service registration or renewal, and synchronize the provider service registration information to at least two random nodes in the registration center; The registration center module is used to randomly select nodes to provide external services to the service gateway or application; A self-service portal module is used to periodically obtain the full amount of provider service registration information and its timestamp in the registration center for persistent storage; A monitoring center module, used to monitor each node in the registration center in real time. If it is determined that the data of any node is unavailable, the failure time is recorded and the service gateway is connected to the emergency center module; The emergency center module is used to match the fault time and the timestamp in the self-service portal, load the full provider service registration information corresponding to the fault time, and replace the registration center to provide external services to the service gateway or application.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 6 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

Images