CN113067860B - Method, apparatus, device, medium and product for synchronizing information - Google Patents
Method, apparatus, device, medium and product for synchronizing information Download PDFInfo
- Publication number
- CN113067860B CN113067860B CN202110282108.4A CN202110282108A CN113067860B CN 113067860 B CN113067860 B CN 113067860B CN 202110282108 A CN202110282108 A CN 202110282108A CN 113067860 B CN113067860 B CN 113067860B
- Authority
- CN
- China
- Prior art keywords
- control node
- information
- cluster
- determining
- domain name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0893—Assignment of logical groups to network elements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
Abstract
The application discloses a method, a device, equipment, a medium and a product for synchronizing information, relates to the field of cloud computing, and further relates to the technical field of cloud networks. The specific implementation scheme is as follows: acquiring control node information of each cluster; determining a source control node and a destination control node based on the control node information; acquiring domain name system information sent by a source control node; and synchronizing the domain name system information to the destination control node. The implementation mode can improve the safety of information synchronization.
Description
Technical Field
The present disclosure relates to the field of cloud computing, and further to the field of cloud network technologies, and in particular, to methods, apparatuses, devices, media, and products for synchronizing information.
Background
Currently, in a Cloud computing environment, a Virtual Private Cloud (VPC) can provide a secure and Private Virtual network environment.
In practical applications, it is often necessary to perform connectivity processing on clusters in different VPC environments. At this time, for each cluster performing the connectivity processing, domain Name System (DNS) information of clusters in other VPC environments needs to be acquired, so as to implement DNS information synchronization in different VPC environments.
Generally, the DNS information synchronization is realized by directly accessing the database across clusters, but this method needs to be configured to allow the database to be accessed across clusters due to limited rights for accessing the database between clusters, thereby causing a great safety hazard.
Disclosure of Invention
The present disclosure provides a method, apparatus, device, medium, and article of manufacture for synchronizing information.
According to a first aspect, there is provided a method for synchronizing information, comprising: acquiring control node information of each cluster; determining a source control node and a destination control node based on the control node information; acquiring domain name system information sent by a source control node; and synchronizing the domain name system information to the destination control node.
According to a second aspect, there is provided an apparatus for synchronizing information, comprising: a first information acquisition unit configured to acquire 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; a second information acquisition unit configured to acquire domain name system information transmitted by a source control node; and the information synchronization unit is configured to synchronize the domain name system information to the destination control node.
According to a third aspect, there is provided an electronic device performing a method for synchronizing information, comprising: one or more computing units; a storage unit for storing one or more programs; when executed by one or more computing units, cause the one or more computing units to implement a method for synchronizing information as any one of above.
According to a fourth aspect, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing a computer to perform the method for synchronizing information as any one of the above.
According to a fifth aspect, there is provided a computer program product comprising a computer program which, when executed by a computing unit, implements a method for synchronizing information as any of the above.
According to the technology of the application, a method for synchronizing information is provided, which can determine a source control node needing to send domain name system information and a target control node needing to receive the domain name system information based on control node information of each cluster, and then forward the domain name system information between the source control node and the target control node, so as to realize synchronization of the domain name system information. The process does not need to directly cross the cluster access database, does not need to configure the cross-cluster access authority of the database, and improves the safety of information synchronization.
It should be understood that the statements in this section are not intended to identify key or critical features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
FIG. 1 is an exemplary system architecture diagram in which one embodiment of the present application may be applied;
FIG. 2 is a flow diagram for one 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 flow diagram of another embodiment of a method for synchronizing information according to the present application;
FIG. 5 is a schematic diagram illustrating one embodiment of an apparatus for synchronizing information according to the present application;
FIG. 6 is a block diagram of an electronic device used to implement a method for synchronizing information of an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of the embodiments of the disclosure are included to assist understanding, and which are to be considered as merely exemplary. 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 present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 is an exemplary system architecture diagram according to a first embodiment of the present disclosure, illustrating an exemplary system architecture 100 to which embodiments of the method for synchronizing information of the present application may be applied.
As shown in fig. 1, system architecture 100 may include server 101, network 102, server 103, network 104, and server 105. Network 102 is the medium used to provide communication links between servers 101 and 103. Network 104 is the medium used to provide communication links between server 103 and server 105. Networks 102, 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.
The server 101 may be a server that provides various services, and the server 101 may operate in a VPC environment. Server 103 may act as a proxy for information interaction between server 101 and server 105. The server 103 can perform information interaction with the server 101 through the network 102, and the server 103 can also perform information interaction with the server 105 through the network 104. The server 105 may operate in another VPC environment.
The servers 101, 103, and 105 may be hardware or software. When the servers 101, 103, and 105 are hardware, they may be implemented as a distributed server cluster composed of multiple servers, or may be implemented as a single server. When the servers 101, 103, 105 are software, they may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.
When both the server 101 and the server 105 are a cluster including a plurality of servers and the cluster of the server 101 and the server 105 performs the connection processing, the server 103 may acquire control node information of the cluster of the server 101 and control node information of the cluster of the server 105. Then, based on the control node information, a source control node and a destination control node are determined. For example, the source control node may be a control node in server 101 and the destination control node may be a control node in server 105. After that, the server 103 may 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 embodiments of the present application is generally performed by the server 103. Accordingly, means for synchronizing information is typically provided in the server 103.
It should be understood that the number of servers and networks in fig. 1 is merely illustrative. There may be any number of servers and networks, as desired for the implementation.
With continued reference to FIG. 2, a flow 200 of one embodiment of a method for synchronizing information in accordance with the present application is shown. The method for synchronizing information of the embodiment comprises the following steps:
In this embodiment, the execution subject (e.g., server 103 in fig. 1) may adopt Proxy (Proxy server or Proxy software), and may be used for information interaction between different clusters. In addition, the execution main body may further store relevant configuration information of each cluster, for example, control node information, node correspondence information, and the like of each cluster, which is not limited in this embodiment. The control node information of the cluster is information for describing 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 an Application Programming Interface (API) to perform a corresponding operation based on address information of the API. Wherein different APIs correspond to different operations, such as a read library operation, a write library operation, and the like. That is, the control node may be configured to call the API to perform the corresponding operation. The control node information may include cluster information to which the control node belongs, virtual private cloud environment information corresponding to the control node, and the like. Further, the above clusters may belong to different virtual private cloud environments, and a connection process may be performed between the clusters.
In this embodiment, node correspondence information may also be stored in the execution main body, where the node correspondence information refers to a circulation relationship of domain name system information between the nodes. For example, assuming that the control node information includes information of the control node a, information of the control node B, and information of the control node C, the node correspondence information may include correspondence among the control node a, the control node B, and the control node C, and a flow relationship of domain name system information in the correspondence is that the control node a reads domain name system information in the control node B and the control node C, respectively. At this time, the control node that needs to read the domain name system information and the control node that needs to send the domain name system information may be determined based on the node correspondence information. And then, based on the control node information, determining a cluster to which the control node needing to read the domain name system information belongs and a VPC environment where the control node needs to read the domain name system information, and determining the control node needing to read the domain name system information in the cluster in the VPC environment as a target control node. And determining a cluster to which the control node needing to send the domain name system information belongs and a VPC environment to which the control node belongs based on the control node information. Then, a control node which needs to send domain name system information is determined as a source control node in the cluster in the VPC environment.
In this embodiment, the execution subject may establish a connection relationship with the source control node, and receive domain name system information sent by the source control node. The domain name system information refers to information for mapping a private domain name to a resource internet protocol address, and can be used for resolving the domain name in a VPC environment and mapping the domain name to the corresponding resource internet protocol address. The source control node may 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 a resource isolation characteristic, that is, domain name system information configured in a certain VPC environment does not affect 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, respectively, domain name system information in the cluster at the opposite end needs to be read when performing communication processing between the clusters. In this application scenario, the execution subject may be used as a transfer of information interaction between two clusters.
And step 204, synchronizing the domain name system information to the destination control node.
In this embodiment, the execution subject may forward the domain name system information to the destination control node after acquiring the domain name system information, so that the destination control node acquires the domain name system information, and thereby the domain name system information is synchronized.
With continued reference to fig. 3, a schematic diagram of an application scenario of the method for synchronizing information according to the present application is shown. In the application scenario of fig. 3, there are two clusters, cluster a301 and cluster B303. The cluster a301 at least includes a source control node 3011 and a database 3012, and the cluster B303 at least includes a destination control node 3031 and a database 3032. And cluster a301 may be in a first VPC environment, cluster B303 may be in a second VPC environment, and cluster connectivity is opened between cluster a301 and cluster B303. For cluster a301, it needs to access domain name system information of cluster B303; for cluster B303, access to the domain name system information for cluster a301 is required. At this time, information forwarding needs to be implemented based on the proxy server 302 to obtain domain name system information in the peer-to-peer cluster. First, the proxy server 302 may store the control node information of the cluster a301 and the control node information of the cluster B303, taking only the case where the cluster B303 accesses the domain name system information in the cluster a301 as an example. The proxy server 302 may determine that the cluster B303 needs to access the domain name system information in the cluster a301 at this time based on the control node information, and then the source control node 3011 acquires the domain name system information of the cluster a from the database 3012 and sends the domain name system information to the proxy server 302. Finally, the proxy server 302 may forward the domain name system information sent by the source control node 3011 to the destination control node 3031 after acquiring the domain name system information. Optionally, the destination control node 3031 may also transmit the domain name system information to the database 3032 for storage. On the contrary, if the cluster a301 needs to access the domain name system information in the cluster B303, the control node in the cluster B303 may be used as the source control node, and the control node in the cluster a301 may be used as the destination control node, and other steps please refer to the description when the cluster B303 accesses the domain name system information in the cluster a301, which is not described herein again.
The method for synchronizing information provided in the foregoing embodiment of the present application can determine, based on the control node information of each cluster, a source control node that needs to send domain name system information, and determine a destination control node that needs to receive domain name system information, and then forward the domain name system information between the source control node and the destination control node, thereby implementing synchronization of the domain name system information. The process does not need to directly cross the cluster access database, does not need to configure the cross-cluster access authority of the database, and improves the safety of information synchronization.
With continued reference to FIG. 4, a flow 400 of another embodiment of a method for synchronizing information in accordance with the present application is shown. As shown in fig. 4, the method for synchronizing information of the present embodiment may include the steps of:
In this embodiment, the control node information acquired by the execution subject may be control node information in each Virtual Private Cloud (VPC) environment. 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 obtaining process of the control node information, please refer to the detailed description of step 201, which is not described herein again.
In some optional implementations of this embodiment, the following steps may also be performed: the control node information is updated periodically.
In this implementation manner, the control node information may change with the deployment of the new cluster, the deletion of the cluster, the change of the cluster, and the like. Therefore, the execution main body can improve the accuracy of the control node information by adopting a preset updating period and a mode of regularly updating the control node information. Alternatively, the execution main body may also detect whether a trigger condition exists for updating the control node information, and if so, automatically update the control node information. The triggering condition may be that a new cluster deployment exists, a cluster deletion or change exists, and the like, which is not limited in this embodiment.
In this embodiment, each cluster in the cluster set has a connectivity relationship, where the connectivity relationship at least includes a relationship that enables access to the service domain name in each cluster. The execution main body can divide each cluster corresponding to the control node information into cluster sets according to the communication relation, and therefore each cluster set with the communication relation is determined.
Determining a cluster set having a connected relationship among the clusters may include the following steps: detecting cluster groups executing the connected operation in each cluster, and adding the same connected mark to each cluster in the cluster groups executing the connected operation; in each cluster, the clusters with the same connected mark are determined as a cluster set with connected relation. By executing the step, whether the cluster is executed with the communication operation or not can be detected, if the cluster is detected to be executed with the communication operation, the same communication mark can be added to the communicated clusters, then, the clusters can be divided by counting the communication marks to obtain at least one cluster set with the communication relation, and the determining efficiency of the cluster sets is improved.
In this embodiment, the execution subject may determine each cluster included in the cluster set, and then determine each control node matched with 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 a party that sends domain name system information, and the information receiver refers to a party that receives domain name system information. The information synchronization process refers to a process of synchronizing domain name system information transmitted from an information transmitting side to an information receiving side. Therefore, the execution body may determine the information sender as a source control node and the information receiver as a destination control node from the control nodes to achieve 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, determining an information receiving type corresponding to the control node, wherein the information receiving type is information receiving or information sending, and each control node can simultaneously correspond to two information receiving types; then, for the control node, determining a node list corresponding to the information receiving type of the control node, wherein the node list comprises one or more other control nodes except the control node; for each control node, determining the node with the information type of information transmission as a source control node; and for each source control node, determining each control node in the node list corresponding to the information sending type as a destination control node corresponding to the source control node. Or, for each control node, determining the node with the information type of information receiving as the target control node; and for each destination control node, determining each control node in the node list corresponding to the information receiving with the information type as a source control node corresponding to the destination control node.
In some optional implementations of this embodiment, determining an information sender in the control node as a source control node and determining an information receiver in the control node as a destination control node includes: in response to detecting that a new cluster exists in the cluster set, the control node of the new cluster is determined as a source control node, and the control nodes of other clusters in the cluster set except the new cluster are determined as destination control nodes.
In this implementation, the new cluster refers to a newly deployed cluster, and other clusters in the same cluster set do not synchronize domain name system information in the cluster. The execution subject may detect whether a new cluster exists in the cluster set, and if it is detected that a new cluster exists, may determine the control node of the new cluster as a source control node, that is, a node that sends domain name system information. Then, the control nodes of the clusters other than the new cluster in the cluster set may be determined as the destination control node, that is, the node receiving the domain name system information. In this way, the domain name system information in the newly deployed cluster can be synchronized to each of the old clusters. That is, when a new cluster is expanded, only the domain name system information needs to be forwarded by the executing main body, the information synchronization of the old cluster can be realized, the configuration information matched with the old cluster does not need to be modified, and the expansion efficiency is higher.
In this embodiment, the execution subject may determine a source cluster to which the source control node belongs, and the source cluster may include the source control node and a database.
And 406, acquiring domain name system information acquired by the source control node from a database in the source cluster.
In this embodiment, the database in the source cluster may store domain name system information of the source cluster, and the source control node may access the database to obtain the domain name system information and then send the domain name system information to the execution subject.
In this embodiment, please refer to the detailed description of step 204 for the detailed description of step 407, which is not repeated herein.
Optionally, after step 407 is executed, the following steps may also be executed: determining a target cluster to which a target control node belongs, wherein the target cluster comprises the target control node and a database; and responding to the detection that the destination control node sends the domain name system information to a database of the destination cluster, and recording data synchronization data, wherein the data synchronization data can comprise the source control node, the destination control node and a data synchronization success identifier. By executing the step, the information synchronization condition of the domain name system information can be recorded, so that the probability of repeatedly executing the information synchronization condition is reduced, and the information synchronization effect is improved.
The method for synchronizing information provided in the foregoing embodiment of the present application may also reduce data redundancy by forwarding domain name system information of a new cluster through a proxy server or a proxy service without modifying configuration information in an old cluster of an inventory in a cluster capacity expansion scenario. In addition, the 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 through the proxy server or the proxy service. Only the database of the same cluster needs to be accessed, and the database does not need to be accessed directly across clusters, so that the information synchronization safety is improved. Moreover, for the way of directly accessing the database across clusters, each time the cluster is expanded, the database in the old cluster needs to be kept to set the access authority for the new cluster, and the operation is complex. In addition, by adopting the method for synchronizing the information provided by the embodiment, the database does not need to be accessed directly across the clusters, so that the performance pressure of the database can be reduced, and the information synchronization performance can be improved.
With further reference to fig. 5, as an implementation of the methods shown in the above-mentioned figures, the present application provides an embodiment of an apparatus for synchronizing information, which corresponds to the method embodiment shown in fig. 2, and which is specifically applicable to various servers.
As shown in fig. 5, the apparatus 500 for synchronizing information of the present embodiment includes: a first information acquisition unit 501, a node determination unit 502, a second information acquisition unit 503, and an information synchronization unit 504.
A first information acquisition unit 501 configured to acquire control node information of each cluster.
A node determining unit 502 configured to determine a source control node and a destination control node based on the control node information.
A second information obtaining unit 503, configured to obtain domain name system information sent by the source control node.
An information synchronization unit 504 configured to synchronize domain name system information to the destination control node.
In some optional implementations of this embodiment, the second information obtaining unit 503 is further configured to: determining a source cluster to which a source control node belongs; and acquiring domain name system information acquired by the source control node from a database in the source cluster.
In some optional implementations of this embodiment, the node determining unit 502 is further configured to: determining a cluster set with a connected relation in each cluster; determining a control node in the cluster set based on the control node information; an information sender in the control node is determined as a source control node, and an information receiver in the control node is determined as a 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, the control node of the new cluster is determined as a source control node, and the control nodes of other clusters in the cluster set except the new cluster are determined as destination control nodes.
In some optional implementations of the present embodiment, the first information obtaining unit 501 is further configured to: and for each virtual private cloud, acquiring control node information of each cluster in the virtual private cloud environment.
In some optional implementations of this embodiment, the apparatus further includes: an information updating unit configured to periodically update the control node information.
The apparatus for synchronizing information provided in the foregoing embodiment of the present application can determine, based on the control node information of each cluster, a source control node that needs to send domain name system information, and determine a destination control node that needs to receive domain name system information, and then forward the domain name system information between the source control node and the destination control node, thereby implementing synchronization of the domain name system information. The process does not need to directly cross the cluster access database, does not need to configure the cross-cluster access authority of the database, and improves the safety of information synchronization.
It should be understood that the units 501 to 504, which are described in the apparatus 500 for synchronizing information, correspond to the respective steps in the method described with reference to fig. 2, respectively. Thus, the operations and features described above for the method using synchronization information are equally applicable to the apparatus 500 and the units included therein, and are not described in detail here.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present application.
FIG. 6 shows a block diagram of an electronic device 600 used to implement the method for synchronizing information of an embodiment of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 6, the device 600 comprises a computing unit 601, which may perform various suitable actions and processes 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. In the RAM 603, various programs and data required 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 via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
A number of components in the device 600 are connected to the I/O interface 605, including: an input unit 606 such as a keyboard, a mouse, or the like; an output unit 607 such as various types of displays, speakers, and the like; a storage unit 608, such as a magnetic disk, optical disk, or the like; and a communication unit 609 such as a network card, modem, wireless communication transceiver, etc. The communication unit 609 allows the device 600 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
The computing unit 601 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various dedicated Artificial Intelligence (AI) computing chips, various computing units running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, and so forth. The calculation unit 601 performs the respective methods and processes described above, such as the 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 the RAM 603 and executed by the 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 by any other suitable means (e.g., by means of firmware) to perform the method for synchronizing information.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code 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, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. 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 this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The 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, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here 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 a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user may provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present disclosure may be executed in parallel, sequentially or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the scope of protection of the present disclosure.
Claims (10)
1. A method for synchronizing information, comprising:
acquiring control node information of each cluster, including: for each virtual private cloud, acquiring control node information of each cluster in the virtual private cloud environment;
determining a source control node and a destination control node based on the control node information, comprising: determining a cluster set with a connection relationship in each cluster, wherein the connection relationship comprises a relationship of mutually accessing service domain names in each cluster; determining each control node in the cluster set based on the control node information; based on the information receiving type corresponding to each control node, determining an information sending party in each control node as the source control node, and determining an information receiving party in each control node as the destination control node, wherein the information receiving type comprises information receiving or information sending;
acquiring domain name system information sent by the source control node;
and synchronizing the domain name system information to the destination control node.
2. The method according to claim 1, wherein the obtaining domain name system information sent by the source control node includes:
determining a source cluster to which the source control node belongs;
and acquiring the domain name system information acquired by the source control node from a database in the source cluster.
3. The method of claim 1, wherein the determining an information sender in the control node as the source control node and an information receiver in the control node as the destination control node comprises:
in response to detecting that a new cluster exists in the set of clusters, determining a control node of the new cluster as the source control node and determining control nodes of other clusters in the set of clusters except the new cluster as the destination control node.
4. The method of claim 1, wherein the method further comprises:
and updating the control node information periodically.
5. An apparatus for synchronizing information, comprising:
a first information acquisition unit configured to acquire 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;
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;
the node determination unit is further configured to:
determining a cluster set with a connection relationship in each cluster, wherein the connection relationship comprises a relationship of mutually accessing service domain names in each cluster;
determining each control node in the cluster set based on the control node information;
based on the information receiving type corresponding to each control node, determining an information sending party in each control node as the source control node, and determining an information receiving party in each control node as the destination control node, wherein the information receiving type comprises information receiving or information sending;
the first information acquisition unit is further configured to:
and for each virtual private cloud, acquiring control node information of each cluster in the virtual private cloud environment.
6. The apparatus of claim 5, wherein the second information acquisition unit is further configured to:
determining a source cluster to which the source control node belongs;
and acquiring the domain name system information acquired by the source control node from a database in the source cluster.
7. The apparatus of 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 a control node of the new cluster as the source control node and determining control nodes of other clusters in the set of clusters except the new cluster as the destination control node.
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 that performs a method for synchronizing information, comprising:
at least one computing unit; and
a storage unit communicatively coupled to the at least one computing unit; wherein the content of the first and second substances,
the storage unit stores instructions executable by the at least one computing unit to enable the at least one computing unit to perform the method of any of claims 1-4.
10. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110282108.4A CN113067860B (en) | 2021-03-16 | 2021-03-16 | Method, apparatus, device, medium and product for synchronizing information |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110282108.4A CN113067860B (en) | 2021-03-16 | 2021-03-16 | Method, apparatus, device, medium and product for synchronizing information |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113067860A CN113067860A (en) | 2021-07-02 |
| CN113067860B true CN113067860B (en) | 2022-11-11 |
Family
ID=76560652
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110282108.4A Active CN113067860B (en) | 2021-03-16 | 2021-03-16 | Method, apparatus, device, medium and product for synchronizing information |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113067860B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113542451B (en) * | 2021-07-30 | 2023-11-03 | 阿波罗智联(北京)科技有限公司 | Information processing method, device, equipment and storage medium |
| CN114726871A (en) * | 2022-03-22 | 2022-07-08 | 阿里巴巴（中国）有限公司 | Data synchronization method, device and network system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111510367A (en) * | 2020-04-17 | 2020-08-07 | 上海思询信息科技有限公司 | VPC network cross-cluster intercommunication realization method and system based on VX L AN tunnel |
| CN111818194A (en) * | 2020-07-01 | 2020-10-23 | 中国建设银行股份有限公司 | Domain name based access system and method |
| CN111885123A (en) * | 2020-07-06 | 2020-11-03 | 苏州浪潮智能科技有限公司 | Construction method and device of cross-K8 s target service access channel |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9866475B2 (en) * | 2012-06-15 | 2018-01-09 | Citrix Systems, Inc. | Systems and methods for forwarding traffic in a cluster network |
-
2021
- 2021-03-16 CN CN202110282108.4A patent/CN113067860B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111510367A (en) * | 2020-04-17 | 2020-08-07 | 上海思询信息科技有限公司 | VPC network cross-cluster intercommunication realization method and system based on VX L AN tunnel |
| CN111818194A (en) * | 2020-07-01 | 2020-10-23 | 中国建设银行股份有限公司 | Domain name based access system and method |
| CN111885123A (en) * | 2020-07-06 | 2020-11-03 | 苏州浪潮智能科技有限公司 | Construction method and device of cross-K8 s target service access channel |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113067860A (en) | 2021-07-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108712332B (en) | Communication method, system and device | |
| CN103019960B (en) | Distributed caching method and system | |
| CN112583931B (en) | Message processing method, message middleware, electronic device, and storage medium | |
| CN113067860B (en) | Method, apparatus, device, medium and product for synchronizing information | |
| EP2618278B1 (en) | Synchronizing endpoint data stores having disparate schemas | |
| CN113656501B (en) | Data reading method, device, equipment and storage medium | |
| CN113364877A (en) | Data processing method, device, electronic equipment and medium | |
| US11249854B2 (en) | Method and device for failover in HBase system, and non-transitory computer-readable storage medium | |
| CN111338834A (en) | Data storage method and device | |
| CN112804366B (en) | Method and device for resolving domain name | |
| US20200387412A1 (en) | Method To Manage Database | |
| US9456046B2 (en) | Dynamic generation of proxy connections | |
| JP6364727B2 (en) | Information processing system, distributed processing method, and program | |
| CN112148728A (en) | Method, apparatus and computer program product for information processing | |
| CN112860796B (en) | Method, apparatus, device and storage medium for synchronizing data | |
| CN115277707A (en) | Service processing method, device, electronic equipment and storage medium | |
| CN114760360B (en) | Request response method, request response device, electronic equipment and computer readable storage medium | |
| CN115374078A (en) | Data storage and reading system and working method thereof | |
| CN109918213A (en) | A kind of message treatment method, device and server | |
| CN115118654B (en) | Data forwarding method, system, device and program product under virtual network | |
| US9529549B2 (en) | Data processing method for storing data and restoration information and data processing system | |
| CN114745281B (en) | Data processing method and device | |
| CN114327293B (en) | Data reading method, device, equipment and storage medium | |
| CN110262756B (en) | Method and device for caching data | |
| CN115510036A (en) | Data migration method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |