CN113067860B - Method, apparatus, device, medium and product for synchronizing information - Google Patents

Abstract

The present application discloses a method, apparatus, device, medium and product for synchronizing information, which relates to the field of cloud computing, and further relates to the field of cloud network technology. The specific implementation scheme is as follows: obtaining the control node information of each cluster; determining the source control node and the destination control node based on the control node information; obtaining the domain name system information sent by the source control node; and synchronizing the domain name system information to the destination control node. This implementation manner can improve the security of information synchronization.

Description

Method, device, device, medium and product for synchronizing information

technical field

The present disclosure relates to the field of cloud computing, further relates to the field of cloud network technology, and in particular to a method, device, device, medium and product for synchronizing information.

Background technique

Currently, in a cloud computing environment, a virtual private cloud (Virtual Private Cloud, VPC) can provide a safe and private virtual network environment.

In practical applications, it is often necessary to connect clusters in different VPC environments. At this time, for each cluster performing connection processing, Domain Name System (Domain Name System, DNS) information of clusters in other VPC environments needs to be obtained, so as to realize synchronization of DNS information in different VPC environments.

Usually, DNS information synchronization is achieved by directly accessing databases across clusters. However, due to the limited access to databases between clusters in this way, configurations are required to allow cross-cluster access to databases, which leads to greater security risks.

Contents of the invention

The present disclosure provides a method, device, device, medium and product for synchronizing information.

According to the first aspect, there is provided a method for synchronizing information, including: obtaining control node information of each cluster; determining a source control node and a destination control node based on the control node information; obtaining domain name system information sent by the source control node; Synchronize domain name system information to the destination control node.

According to the second aspect, there is provided an apparatus for synchronizing information, including: a first information acquisition unit configured to acquire control node information of each cluster; a node determination unit configured to determine source control node information based on the control node information A node and a destination control node; a second information obtaining unit configured to obtain domain name system information sent by the source control node; an information synchronization unit configured to synchronize the domain name system information to the destination control node.

According to a third aspect, there is provided an electronic device for executing a method for synchronizing information, including: one or more computing units; a storage unit for storing one or more programs; when one or more programs are used by one or more A plurality of computing units are executed, so that one or more computing units implement any one of the above methods for synchronizing information.

According to a fourth aspect, there is provided a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause a computer to execute any one of the above methods for synchronizing information.

According to a fifth aspect, there is provided a computer program product comprising a computer program which, when executed by a computing unit, implements any of the above methods for synchronizing information.

According to the technology of the present application, a method for synchronizing information is provided, which can determine the source control node that needs to send domain name system information and determine the destination control node that needs to receive domain name system information based on the control node information of each cluster, The domain name system information is forwarded between the source control node and the destination control node to realize the synchronization of the domain name system information. This process does not require direct cross-cluster access to the database, and does not need to configure cross-cluster access permissions for the database, which improves the security of information synchronization.

It should be understood that what is described in this section is not intended to identify key or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will be readily understood through the following description.

Description of drawings

The accompanying drawings are used to better understand the present solution, and do not constitute a limitation to the present disclosure. in:

FIG. 1 is an exemplary system architecture diagram to which an embodiment of the present application can be applied;

FIG. 2 is a flowchart of an embodiment of a method for synchronizing information according to the present application;

FIG. 3 is a schematic diagram of an application scenario of a method for synchronizing information according to the present application;

FIG. 4 is a flowchart of another embodiment of a method for synchronizing information according to the present application;

FIG. 5 is a schematic structural diagram of an embodiment of a device for synchronizing information according to the present application;

FIG. 6 is a block diagram of an electronic device for implementing the method for synchronizing information according to an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments of the present disclosure are described below in conjunction with the accompanying drawings, which include various details of the embodiments of the present disclosure to facilitate understanding, and they should be regarded as exemplary only. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and embodiments.

Fig. 1 is a schematic diagram of an exemplary system architecture according to a first embodiment of the present disclosure, which shows an exemplary system architecture 100 to which an embodiment of the method for synchronizing information of the present application can be applied.

As shown in FIG. 1 , the system architecture 100 may include a server 101 , a network 102 , a server 103 , a network 104 and a server 105 . The network 102 is used as a medium for providing a communication link between the server 101 and the server 103 . The network 104 is used as a medium for providing a communication link between the server 103 and the server 105 . Networks 102, 104 may include various connection types, such as wires, wireless communication links, or fiber optic cables, among others.

The server 101 may be a server providing various services, and the server 101 may operate under a VPC environment. The server 103 may serve as a proxy server for information exchange between the server 101 and the server 105 . The server 103 can exchange information with the server 101 through the network 102 , and the server 103 can also exchange information with the server 105 through the network 104 . Server 105 may run in another VPC environment.

It should be noted that the servers 101, 103, and 105 may be hardware or software. When the servers 101, 103, and 105 are hardware, they can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the servers 101, 103, and 105 are software, they may be implemented as multiple software or software modules (for example, for providing distributed services), or as a single software or software module. No specific limitation is made here.

When the server 101 and the server 105 are clusters composed of multiple servers, and the clusters of the server 101 and the server 105 have been connected, the server 103 can obtain the control node information of the cluster of the server 101 and the control of the cluster of the server 105 Node information. Afterwards, based on the control node information, the source control node and the destination control node are determined. For example, the source control node may be the control node in the server 101 , and the destination control node may be the control node in the server 105 . Afterwards, the server 103 can obtain the domain name system information sent by the server 101, and then synchronize the domain name system information to the server 105.

It should be noted that, the method for synchronizing information provided in the embodiment of the present application is generally executed by the server 103 . Correspondingly, the means for synchronizing information is usually set in the server 103 .

It should be understood that the numbers of servers and networks in FIG. 1 are merely illustrative. There can be any number of servers and networks depending on implementation needs.

Continuing to refer to FIG. 2 , a flow 200 of an embodiment of a method for synchronizing information according to the present application is shown. The method for synchronizing information in this embodiment includes the following steps:

Step 201, acquiring control node information of each cluster.

In this embodiment, the execution subject (such as the server 103 in FIG. 1 ) can use a Proxy (proxy server or proxy software), which can be used for information exchange between different clusters. In addition, related configuration information of each cluster may also be stored on the execution subject, such as control node information and node correspondence information of each cluster, which is not limited in this embodiment. Wherein, the control node information of the cluster is information used to describe the control node of the cluster, and the control node of the cluster refers to a NET-SERVER (a network control code) node. The control node may call the API to perform corresponding operations based on the address information of the application programming interface (Application Programming Interface, API). Among them, different APIs correspond to different operations, such as library read operations, library write operations, and so on. That is, the control node can be used to call the API to perform corresponding operations. The control node information may include the cluster information to which the control node belongs, the virtual private cloud environment information corresponding to the control node, and the like. Further, each of the aforementioned clusters may belong to different virtual private cloud environments, and connection processing may be performed between these clusters.

Step 202, based on the control node information, determine the source control node and the destination control node.

In this embodiment, node correspondence information may also be stored in the execution subject, wherein the node correspondence information refers to the flow relationship of domain name system information between various nodes. For example, assuming that the control node information includes information on control node A, information on control node B, and information on control node C, the node correspondence information may include that there is a correspondence between control node A, control node B, and control node C, and The domain name system information transfer relationship in the corresponding relationship is that the control node A reads the domain name system information in the control node B and the control node C respectively. At this time, the control nodes that need to read the domain name system information and the control nodes that need to send the domain name system information can be determined based on the node correspondence information. Afterwards, based on the control node information, determine the cluster to which the control node that needs to read domain name system information belongs, the VPC environment where it is located, and determine the control node that needs to read domain name system information in the cluster in the VPC environment as destination control node. And, based on the control node information, determine the cluster to which the control node that needs to send domain name system information belongs and the VPC environment it is in. Afterwards, the control node that needs to send domain name system information is determined in the cluster in the VPC environment as the source control node.

Step 203, obtaining domain name system information sent by the source control node.

In this embodiment, the execution subject can establish a connection relationship with the source control node, and receive domain name system information sent by the source control node. Wherein, the domain name system information refers to the information of mapping the private domain name to the Internet protocol address of the resource, which can be used to resolve the domain name in the VPC environment and map to the corresponding Internet protocol address of the resource. Wherein, the source control node can first read the domain name system information from the database of the same cluster, and then send the domain name system information to the execution subject.

It should be noted that different VPCs have resource isolation characteristics, that is, domain name system information configured in a VPC environment has no impact on other VPC environments. On this basis, if the source control node and the destination control node are in different VPC environments and belong to two independent clusters, it is necessary to read the domain name system information in the peer cluster when performing connection processing between the clusters . In this application scenario, the executive body can be used as the intermediary of information exchange between the two clusters.

Step 204, synchronizing the domain name system information to the destination control node.

In this embodiment, after obtaining the domain name system information, the execution subject may forward the domain name system information to the destination control node, so that the destination control node obtains the domain name system information and realizes the synchronization of the domain name system information.

Continue to refer to FIG. 3 , which shows a schematic diagram of an application scenario of the method for synchronizing information according to the present application. In the application scenario of FIG. 3 , there are two clusters, cluster A301 and cluster B303. Among them, cluster A301 includes at least a source control node 3011 and a database 3012 , and cluster B303 includes at least a destination control node 3031 and a database 3032 . In addition, cluster A301 may be in a first VPC environment, cluster B303 may be in a second VPC environment, and cluster connectivity is established between cluster A301 and cluster B303. For cluster A301, it is necessary to access the domain name system information of cluster B303; for cluster B303, it is necessary to access the domain name system information of cluster A301. At this time, information forwarding needs to be implemented based on the proxy server 302 to obtain domain name system information in the peer cluster. Taking cluster B 303 accessing domain name system information in cluster A 301 as an example, firstly, the proxy server 302 may store the control node information of cluster A 301 and the control node information of cluster B 303 . The proxy server 302 can determine based on the control node information that cluster B 303 needs to access the domain name system information in cluster A 301 at this time, and then the source control node 3011 obtains the domain name system information of cluster A from the database 3012, and then sends the domain name system information to Proxy server 302. Finally, the proxy server 302 may forward the domain name system information to the destination control node 3031 after obtaining the domain name system information sent by the source control node 3011 . Optionally, the destination control node 3031 may also transmit the domain name system information to the database 3032 for storage. Conversely, if cluster A301 needs to access domain name system information in cluster B303, the control node in cluster B303 can be used as the source control node, and the control node in cluster A301 can be used as the destination control node. For other steps, please refer to cluster B303 to access cluster A301 The description of the domain name system information in , will not be repeated here.

The method for synchronizing information provided by the above embodiments of the present application can determine the source control node that needs to send domain name system information and determine the destination control node that needs to receive domain name system information based on the control node information of each cluster, and then The domain name system information is forwarded between the source control node and the destination control node to realize the synchronization of the domain name system information. This process does not require direct cross-cluster access to the database, and does not need to configure cross-cluster access permissions for the database, which improves the security of information synchronization.

Continue referring to FIG. 4 , which shows a flow 400 of another embodiment of the method for synchronizing information according to the present application. As shown in Figure 4, the method for synchronizing information in this embodiment may include the following steps:

Step 401, for each virtual private cloud, obtain control node information of each cluster in the virtual private cloud environment.

In this embodiment, the control node information acquired by the execution subject may be control node information in each virtual private cloud (VPC) environment. Wherein, for each VPC, the number of clusters in the VPC environment may be one or multiple, which is not limited in this embodiment. For the specific acquisition process of the control node information, please refer to the detailed description of step 201, which will not be repeated here.

In some optional implementation manners of this embodiment, the following step may also be performed: periodically updating the control node information.

In this implementation manner, the control node information may change with the deployment of a new cluster, deletion of a cluster, change of a cluster, and the like. Therefore, the executive body can use the preset update cycle to regularly update the control node information to improve the accuracy of the control node information. Alternatively, the execution subject may also detect whether there is a trigger condition for updating the control node information, and if so, automatically update the control node information. Wherein, the trigger condition may be the detection of a new cluster deployment, deletion or change of a cluster, etc., which is not limited in this embodiment.

Step 402, determining a set of clusters having a connected relationship in each cluster.

In this embodiment, each cluster in the cluster set has a connected relationship, wherein the connected relationship at least includes a relationship that enables mutual access to service domain names in each cluster. The execution subject may divide each cluster corresponding to the control node information into cluster sets according to the connection relationship, so as to determine each cluster set with the connection relationship.

Wherein, determining the cluster sets with connected relations in each cluster may include the following steps: detecting cluster groups performing connected operations in each cluster, adding the same connected mark to each cluster in the cluster groups performing connected operations; In , the clusters with the same connected label are determined as the set of clusters with connected relations. By performing this step, it is possible to detect whether the connected operation is performed on the cluster. If it is detected that the connected operation is performed on the cluster, the connected cluster can be added with the same connected mark. After that, each cluster can be divided by counting the connected marks to obtain At least one cluster set of relations improves the efficiency of determining the cluster set.

Step 403, based on the control node information, determine the control node in the cluster set.

In this embodiment, the execution subject may determine each cluster included in the cluster set, and then determine each control node matching each cluster included in the cluster set based on the control node information.

In step 404, the information sender in the control node is determined as the source control node, and the information receiver in the control node is determined as the destination control node.

In this embodiment, the information sender refers to the party that sends the domain name system information, and the information receiver refers to the party that receives the domain name system information. The information synchronization process refers to the process of synchronizing the domain name system information sent by the information sender to the information receiver. Therefore, the execution subject can determine the information sender as the source control node and the information receiver as the destination control node from the control nodes, so as to realize information synchronization.

Wherein, determining the information sender in the control node as the source control node, and determining the information receiver in the control node as the destination control node may include the following steps: For each control node, determine the information receiving type corresponding to the control node , the information receiving type is information receiving or information sending, and each control node can correspond to two types of information receiving at the same time; then, for the control node, determine the node list corresponding to the information receiving type of the control node, in the node list Including one or more control nodes other than the control node; for each control node, the node whose information type is information sending is determined as the source control node; for each source control node, the node corresponding to the information sending type Each control node in the list is determined as the destination control node corresponding to the source control node. Or, for each control node, the node whose information type is information reception is determined as the destination control node; for each destination control node, each control node in the node list corresponding to information reception is determined as the target node The source control node corresponding to the control node.

In some optional implementations of this embodiment, determining the information sender in the control node as the source control node, and determining the information receiver in the control node as the destination control node include: responding to detecting the cluster set There is a new cluster in , determine the control node of the new cluster as the source control node, and determine the control nodes of other clusters in the cluster set except the new cluster as the destination control node.

In this implementation manner, a new cluster refers to a newly deployed cluster, and other clusters in the same cluster set have not synchronized domain name system information in the cluster. The execution subject can detect whether there is a new cluster in the cluster set, and if it detects that there is a new cluster, it can determine the control node of the new cluster as the source control node, that is, the node that sends the domain name system information. Afterwards, control nodes of clusters other than the new cluster in the cluster set may be determined as target control nodes, that is, nodes that receive domain name system information. In this way, the domain name system information in the newly deployed cluster can be synchronized to each old cluster. That is to say, when expanding a new cluster, only the domain name system information needs to be forwarded by the execution subject to synchronize the information of the existing cluster, and there is no need to modify the matching configuration information of the old cluster, and the expansion efficiency is higher.

Step 405, determine the source cluster to which the source control node belongs.

In this embodiment, the execution subject may determine the source cluster to which the source control node belongs, and the source cluster may include the source control node and the database.

Step 406, obtaining domain name system information obtained by the source control node from the database in the source cluster.

In this embodiment, the domain name system information of the source cluster can be stored in the database of the source cluster, and the source control node can access the database to obtain the domain name system information, and then send the domain name system information to the execution subject.

Step 407, synchronizing the domain name system information to the destination control node.

In this embodiment, for the detailed description of step 407, please refer to the detailed description of step 204, which will not be repeated here.

Optionally, after performing step 407, the following steps may also be performed: determine the target cluster to which the target control node belongs, and the target cluster includes the target control node and the database; in response to detecting that the target control node sends domain name system information to the target cluster In the database of , data synchronization data is recorded, wherein the data synchronization data may include the above-mentioned source control node, the above-mentioned destination control node, and an identification of successful data synchronization. By executing this step, the information synchronization of the domain name system information can be recorded, thereby reducing the probability of repeated execution of information synchronization and improving the effect of information synchronization.

The method for synchronizing information provided by the above embodiments of the present application can also be used in the cluster expansion scenario without modifying the configuration information in the existing old cluster, and only needs to forward the domain name system information of the new cluster through a proxy server or proxy service, reducing data redundancy. In addition, domain name system information can be obtained by the source control node accessing the database of the same cluster, and then forwarded to the destination control node via a proxy server or proxy service. It only needs to access the database of the same cluster, without directly accessing the database across clusters, which improves the security of information synchronization. Moreover, for the method of directly accessing the database across clusters, each time the cluster is expanded, the database in the existing cluster needs to set access permissions for the new cluster, and the operation is more complicated. In addition, by adopting the method for synchronizing information provided by the above embodiments, since there is no need to directly access databases across clusters, the performance pressure of the database can be reduced and the performance of information synchronization can be improved.

Further referring to FIG. 5, as an implementation of the methods shown in the above figures, the present application provides an embodiment of a device for synchronizing information. This device embodiment corresponds to the method embodiment shown in FIG. 2, the The device can be specifically applied to various servers.

As shown in FIG. 5 , the apparatus 500 for synchronizing information in this embodiment includes: a first information acquiring unit 501 , a node determining unit 502 , a second information acquiring unit 503 and an information synchronizing unit 504 .

The first information acquiring unit 501 is configured to acquire control node information of each cluster.

The node determining unit 502 is configured to determine a source control node and a destination control node based on the control node information.

The second information obtaining unit 503 is configured to obtain the domain name system information sent by the source control node.

The information synchronization unit 504 is configured to synchronize the domain name system information to the destination control node.

In some optional implementation manners of this embodiment, the second information obtaining unit 503 is further configured to: determine the source cluster to which the source control node belongs; obtain domain name system information obtained by the source control node from a database in the source cluster.

In some optional implementations of this embodiment, the node determination unit 502 is further configured to: determine a cluster set with a connected relationship in each cluster; determine the control node in the cluster set based on the control node information; The information sender in is determined as the source control node, and the information receiver in the control node is determined as the destination control node.

In some optional implementations of this embodiment, the node determining unit 502 is further configured to: in response to detecting that a new cluster exists in the cluster set, determine the control node of the new cluster as the source control node, and set the Control nodes of clusters other than the new cluster are determined as target control nodes.

In some optional implementation manners of this embodiment, the first information obtaining unit 501 is further configured to: for each virtual private cloud, obtain control node information of each cluster in the virtual private cloud environment.

In some optional implementation manners of this embodiment, the foregoing apparatus further includes: an information updating unit configured to periodically update the control node information.

The device for synchronizing information provided by the above embodiments of the present application can determine the source control node that needs to send domain name system information and determine the destination control node that needs to receive domain name system information based on the control node information of each cluster, and then The domain name system information is forwarded between the source control node and the destination control node to realize the synchronization of the domain name system information. This process does not require direct cross-cluster access to the database, and does not need to configure cross-cluster access permissions for the database, which improves the security of information synchronization.

It should be understood that the units 501 to 504 recorded in the apparatus 500 for synchronizing information respectively correspond to the steps in the method described with reference to FIG. 2 . Therefore, the operations and features described above for the method of synchronizing information are also applicable to the device 500 and the units contained therein, and will not be repeated here.

According to the embodiments of the present application, the present disclosure also provides an electronic device, a readable storage medium, and a computer program product.

FIG. 6 shows a block diagram of an electronic device 600 for implementing the method for synchronizing information according to an embodiment of the present disclosure. Electronic device is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other suitable computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processing, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are by way of example only, and are not intended to limit implementations of the disclosure described and/or claimed herein.

As shown in FIG. 6, the device 600 includes a computing unit 601 that can execute according to a computer program stored in a read-only memory (ROM) 602 or loaded from a storage unit 608 into a random-access memory (RAM) 603. Various appropriate actions and treatments. In the RAM 603, various programs and data necessary for the operation of the device 600 can also be stored. The calculation unit 601 , the ROM 602 and the RAM 603 are connected to each other through a bus 604 . An input/output (I/O) interface 605 is also connected to the bus 604 .

Multiple components in the device 600 are connected to the I/O interface 605, including: an input unit 606, such as a keyboard, a mouse, etc.; an output unit 607, such as various types of displays, speakers, etc.; a storage unit 608, such as a magnetic disk, an optical disk, etc. ; and a communication unit 609, such as a network card, a modem, a wireless communication transceiver, and the like. The communication unit 609 allows the device 600 to exchange information/data with other devices over a computer network such as the Internet and/or various telecommunication networks.

The computing unit 601 may be various general-purpose and/or special-purpose processing components having processing and computing capabilities. Some examples of computing units 601 include, but are not limited to, central processing units (CPUs), graphics processing units (GPUs), various dedicated artificial intelligence (AI) computing chips, various computing units that run machine learning model algorithms, digital signal processing processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 executes various methods and processes described above, such as a method for synchronizing information. For example, in some embodiments, the method for synchronizing information may be implemented as a computer software program tangibly embodied on a machine-readable medium, such as storage unit 608 . In some embodiments, part or all of the computer program may be loaded and/or installed onto the device 600 via the ROM 602 and/or the communication unit 609 . When the computer program is loaded into RAM 603 and executed by computing unit 601, one or more steps of the method for synchronizing information described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured in any other suitable way (for example, by means of firmware) to execute the method for synchronizing information.

Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips Implemented in a system of systems (SOC), load programmable logic device (CPLD), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include being implemented in one or more computer programs executable and/or interpreted on a programmable system including at least one programmable processor, the programmable processor Can be special-purpose or general-purpose programmable processor, can receive data and instruction from storage system, at least one input device, and at least one output device, and transmit data and instruction to this storage system, this at least one input device, and this at least one output device an output device.

Program codes for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general-purpose computer, a special purpose computer, or other programmable data processing devices, so that the program codes, when executed by the processor or controller, make the functions/functions specified in the flow diagrams and/or block diagrams Action is implemented. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media would include one or more wire-based electrical connections, portable computer discs, hard drives, random access memory (RAM), read only memory (ROM), erasable programmable read only memory (EPROM or flash memory), optical fiber, compact disk read only memory (CD-ROM), optical storage, magnetic storage, or any suitable combination of the foregoing.

To provide for interaction with the user, the systems and techniques described herein can be implemented on a computer having a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user. ); and a keyboard and pointing device (eg, a mouse or a trackball) through which a user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and can be in any form (including Acoustic input, speech input or, tactile input) to receive input from the user.

The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., as a a user computer having a graphical user interface or web browser through which a user can interact with embodiments of the systems and techniques described herein), or including such backend components, middleware components, Or any combination of front-end components in a computing system. The components of the system can be interconnected by any form or medium of digital data communication, eg, a communication network. Examples of communication networks include: Local Area Network (LAN), Wide Area Network (WAN) and the Internet.

A computer system may include clients and servers. Clients and servers are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by computer programs running on the respective computers and having a client-server relationship to each other.

It should be understood that steps may be reordered, added or deleted using the various forms of flow shown above. For example, each step described in the present disclosure may be executed in parallel, sequentially, or in a different order, as long as the desired result of the technical solution disclosed in the present disclosure can be achieved, no limitation is imposed herein.

The specific implementation manners described above do not limit the protection scope of the present disclosure. It should be apparent to those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made depending on design requirements and other factors. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present disclosure shall be included within the protection scope of the present disclosure.

Claims (10)

1. A method for synchronizing information, comprising: Obtaining the control node information of each cluster, including: for each virtual private cloud, obtaining the control node information of each cluster in the virtual private cloud environment; Based on the control node information, determining the source control node and the destination control node includes: determining a cluster set with a connection relationship in each cluster, wherein the connection relationship includes a relationship of mutual access to service domain names in each cluster; The control node information is used to determine each control node in the cluster set; based on the information receiving type corresponding to each control node, the information sender in each control node is determined as the source control node, and the source control node in each control node The information receiver is determined as the destination control node, wherein the information receiving type includes information receiving or information sending; Obtain domain name system information sent by the source control node; Synchronize the domain name system information to the destination control node. 2. The method according to claim 1, wherein said acquiring the domain name system information sent by said source control node comprises: determining the source cluster to which the source control node belongs; Obtain the domain name system information acquired by the source control node from the database in the source cluster. 3. The method according to claim 1, wherein said determining the information sender in the control node as the source control node, and determining the information receiver in the control node as the destination control node nodes, including: In response to detecting that a new cluster exists in the set of clusters, determining the control node of the new cluster as the source control node, and determining the control nodes of other clusters in the set of clusters except the new cluster Control the node for said purpose. 4. The method of claim 1, wherein the method further comprises: Periodically update the control node information. 5. An apparatus for synchronizing information, comprising: The first information obtaining unit is configured to obtain control node information of each cluster; a node determination unit configured to determine a source control node and a destination control node based on the control node information; The second information obtaining unit is configured to obtain the domain name system information sent by the source control node; an information synchronization unit configured to synchronize the Domain Name System information to the destination control node; The node determination unit is further configured to: Determining a set of clusters having a connected relationship in each cluster, wherein the connected relationship includes a relationship of mutual access to service domain names in each cluster; Determine each control node in the cluster set based on the control node information; Based on the information receiving type corresponding to each control node, determine the information sender in each control node as the source control node, and determine the information receiver in each control node as the destination control node, wherein the The information receiving type includes information receiving or information sending; The first information acquisition unit is further configured to: For each virtual private cloud, the control node information of each cluster in the virtual private cloud environment is acquired. 6. The device according to claim 5, wherein the second information obtaining unit is further configured to: determining the source cluster to which the source control node belongs; Obtain the domain name system information acquired by the source control node from the database in the source cluster. 7. The apparatus according to claim 5, wherein the node determination unit is further configured to: In response to detecting that a new cluster exists in the set of clusters, determining the control node of the new cluster as the source control node, and determining the control nodes of other clusters in the set of clusters except the new cluster Control the node for said purpose. 8. The apparatus of claim 5, wherein the apparatus further comprises: An information updating unit configured to periodically update the control node information. 9. An electronic device for performing a method for synchronizing information, comprising: at least one computing unit; and a storage unit communicatively connected to the at least one computing unit; wherein, The storage unit stores instructions that can be executed by the at least one computing unit, and the instructions are executed by the at least one computing unit, so that the at least one computing unit can perform any one of claims 1-4. described method. 10. A non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to execute the method according to any one of claims 1-4.

Images