CN109344202B - Data synchronization method and management node - Google Patents

Data synchronization method and management node Download PDF

Info

Publication number
CN109344202B
CN109344202B CN201811284990.0A CN201811284990A CN109344202B CN 109344202 B CN109344202 B CN 109344202B CN 201811284990 A CN201811284990 A CN 201811284990A CN 109344202 B CN109344202 B CN 109344202B
Authority
CN
China
Prior art keywords
management node
postgres database
attribute information
postgres
data
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
Application number
CN201811284990.0A
Other languages
Chinese (zh)
Other versions
CN109344202A (en
Inventor
彭聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Big Data Technologies Co Ltd
Original Assignee
New H3C Big Data Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Big Data Technologies Co Ltd filed Critical New H3C Big Data Technologies Co Ltd
Priority to CN201811284990.0A priority Critical patent/CN109344202B/en
Publication of CN109344202A publication Critical patent/CN109344202A/en
Application granted granted Critical
Publication of CN109344202B publication Critical patent/CN109344202B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/1658—Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/80—Database-specific techniques

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The embodiment of the application provides a data synchronization method and a management node. The method is applied to management nodes in a big data management system, wherein the management nodes comprise a main management node and a standby management node, and the method comprises the following steps: the method comprises the steps that a main management node sends attribute information of a first postgres database corresponding to the main management node to a Dynamic Host Configuration Protocol (DHCP) server periodically; the standby management node periodically requests attribute information of a first postgres database from a DHCP server; and the standby management node synchronizes the data of the first postgres database to the second postgres database when determining that the acquired attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node. Therefore, the operation reliability of the big data integrated management platform can be improved.

Description

Data synchronization method and management node
Technical Field
The embodiment of the application relates to the technical field of data processing, in particular to a data synchronization method and a management node.
Background
The existing big data integration management platform comprises three types of nodes: management node, control node and data node.
A management system (Manager) of the cluster is deployed on the management node, and the Manager provides a uniform access entrance and performs centralized management on various nodes and services in the cluster. In order to realize high availability of the management plane of the big data cluster, the Manager ha service may be started, at this time, a standby Manager may be started on another node in the big data cluster, and a single point of failure of the management node may be prevented by mutual backup between a master management node (MasterManager) and a standby management node (standby Manager). When the main management node fails and cannot access, the standby management node is automatically activated to ensure normal operation of service.
After the primary management node and the standby management node in the big data cluster are switched once, if the current primary management node fails again, the secondary primary-standby switching fails due to the fact that the Postgres database of the standby management node is not synchronized with the Postgres database of the primary management node in time, and finally the service cannot normally run.
Disclosure of Invention
In view of the above, an object of the present application is to provide a data synchronization method and a management node, so as to implement automatic data synchronization.
In a first aspect, an embodiment of the present application provides a data synchronization method, which is applied to a management node in a big data management system, where the management node includes a primary management node and a standby management node, and the method includes:
the master management node periodically sends attribute information of a first postgres database corresponding to the master management node to a Dynamic Host Configuration Protocol (DHCP) server;
the standby management node periodically requests attribute information of the first postgres database from the DHCP server;
and the standby management node determines that the acquired attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node, and synchronizes the data of the first postgres database to the second postgres database.
In a second aspect, an embodiment of the present application provides a management node, including: a main management node and a standby management node;
the master management node is configured to: periodically sending attribute information of a first postgres database corresponding to the main management node to a DHCP server;
the standby management node is configured to: periodically requesting attribute information of the first postgres database from the DHCP server;
and synchronizing the data of the first postgres database to the second postgres database when the obtained attribute information of the first postgres database is determined to be different from the attribute information of the second postgres database corresponding to the first postgres database.
In a third aspect, an embodiment of the present application provides a computer device, which includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the steps of the above method when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, performs the steps of the method described above.
Compared with the prior art, the embodiment of the application has the following beneficial effects: the method comprises the steps that a main management node periodically sends attribute information of a first postgres database corresponding to the main management node to a DHCP server in operation, a standby management node periodically requests the DHCP server to acquire the attribute information of the first postgres database corresponding to the main management node, and the standby management node synchronizes data of the first postgres database to a second postgres database when the acquired attribute information of the first postgres database is determined to be different from the attribute information of the second postgres database corresponding to the standby management node. Furthermore, in the present application, data in databases corresponding to the main management node and the standby management node respectively can be kept in a synchronous state, after the main management node is abnormal, the standby management node can be smoothly switched to be a current main management node, the main management node after the switching is completed can also regularly send attribute information of a first postgres database corresponding to the main management node to the DHCP server, the current standby management node can regularly request the DHCP server for the attribute information of the first postgres database corresponding to the current main management node, and when it is determined that the attribute information of a second postgres database of the standby management node is different from the attribute information of the first postgres database, data synchronization is performed; therefore, even when the current main management node fails again, the second main/standby switching can be smoothly performed due to the data synchronization between the current standby management node and the database of the current main management node, and the normal operation of the service is guaranteed; the method has the positive effect of high reliability, and can improve the user experience.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained according to the drawings without inventive efforts.
Fig. 1 is a schematic flowchart of a data synchronization method according to an embodiment of the present application;
fig. 2 is a schematic diagram of message transmission in a data synchronization process according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a management node according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations.
Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, it need not be further defined and explained in subsequent figures.
In the description of the present application, it is further noted that, unless expressly stated or limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art.
Fig. 1 shows a flowchart of a data synchronization method provided in an embodiment of the present application. The method is applied to management nodes in a big data management system, wherein the management nodes comprise a main management node and a standby management node; the main management node and the standby management node respectively correspond to a postgres database, which respectively comprises: a first postgres database and a second postgres database; referring to fig. 1, the method includes the steps of:
step 101, the active management node periodically sends attribute information of a first postgres database corresponding to the active management node to a dynamic host configuration protocol DHCP server.
In this embodiment of the present application, during a normal operation process, the active management node periodically sends attribute information of a first postgres database corresponding to the active management node to a DHCP (Dynamic Host Configuration Protocol) server. And the DHCP server receives the attribute information of the first postgres database sent by the main management node and stores the attribute information.
And 102, the standby management node periodically requests the attribute information of the first postgres database from the DHCP server.
In the embodiment of the present application, the standby management node periodically sends a request to the DHCP server to obtain the attribute information of the first postgres database corresponding to the active management node.
Step 103, the standby management node synchronizes the data of the first postgres database to the second postgres database when determining that the acquired attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node.
After acquiring the attribute information of the first postgres database corresponding to the main management node from the DHCP server, the standby management node compares the attribute information of the first postgres database with the attribute information of the second postgres database corresponding to the standby management node, and synchronizes the data of the first postgres database to the second postgres database when the attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node.
The synchronization of the data of the first postgres database to the second postgres database can be realized by adopting a mode in the prior art such as a Pacemaker hosting mode.
The attribute information of the database at least includes: database data size information and metadata information; and may also include time information of the latest update of the database, etc.
Furthermore, the standby management node compares the data size and the metadata information of the first postgres database corresponding to the main management node with the data size and the metadata information of the second postgres database corresponding to the standby management node, and when any one of the following conditions is determined to occur: the data size of the first postgres database is different from the data size of the second postgres database; metadata information of a first postgres database and metadata information of a second postgres database; the data size and the metadata information of the first postgres database are different from those of the second postgres database; data from the first postgres database is synchronized to the second postgres database.
In the embodiment of the application, a main management node can regularly send attribute information of a first postgres database corresponding to the main management node to a DHCP server in the operation process, and the DHCP server receives and stores the attribute information of the first postgres database; the standby management node periodically requests a DHCP server to acquire attribute information of a first postgres database corresponding to the main management node, the DHCP server sends the attribute information of the first postgres database to the standby management node, and the standby management node synchronizes data of the first postgres database to a second postgres database when determining that the acquired attribute information of the first postgres database is different from the attribute information of a second postgres database corresponding to the standby management node. Furthermore, in the application, the data in the databases corresponding to the primary management node and the standby management node can be kept in a synchronous state, and after the primary management node is abnormal, the standby management node can be smoothly switched to be the current primary management node. After the switching is completed, the current main management node and the current standby management node also carry out data synchronization according to the method, so that even when the current main management node fails again, the secondary main/standby switching can be smoothly carried out, and the normal operation of the service is ensured; the operation reliability of the big data integration management platform is improved, and the user experience is improved.
In an embodiment of the present application, in the step 101, the periodically sending, by the active management node, the attribute information of the first postgres database corresponding to the active management node to the dynamic host configuration protocol DHCP server includes the following step a 10:
step a10, the primary management node periodically detects whether the data in the first postgres database is updated, and sends the attribute information of the first postgres database corresponding to the primary management node to the DHCP server after the update is detected.
Furthermore, in this embodiment of the present application, the active management node may periodically detect whether data in the first postgres database corresponding to the active management node is updated, for example, whether data addition or deletion occurs, and when it is detected that the data is updated, send attribute information of the first postgres database corresponding to the active management node to the DHCP server. Therefore, the situation that the attribute information of the first postgres database is repeatedly reported to the DHCP server under the condition that the data in the first postgres database is not updated can be avoided.
Fig. 2 is a schematic diagram of message transmission in a data synchronization process according to an embodiment of the present application. Referring to fig. 2, in the embodiment of the present application, in step 102, the step of the standby management node periodically requesting the DHCP server for attribute information of the first postgres database includes the following step B10:
step B10, the standby management node periodically broadcasts a DHCP DISCOVER message, where the DHCP DISCOVER message includes an identifier that represents attribute information of a first postgres database corresponding to the main management node.
After receiving the DHCP DISCOVER message and judging that the DHCP message contains the attribute information of the first postgres database corresponding to the main management node, the DHCP server sends the attribute information of the first postgres database corresponding to the main management node to the standby management node through DHCP PFFER messages.
Specifically, the standby management node broadcasts a DHCP DISCOVER message periodically, where the DHCP DISCOVER message includes an identifier that represents attribute information of a first postgres database corresponding to the application master management node. The DHCP DISCOVER message also includes a destination address for discovering the DHCP server, for example, the destination address includes: the destination IP address is 255.255.255.255, and the destination MAC address is FFFF-FFFF-FFFF.
After receiving the DHCP DISCOVER message, if the DHCP server determines that the message contains an identifier representing the attribute information of the first postgres database corresponding to the main management node, the DHCP server does not process the message according to a mode specified by a DHCP protocol, but obtains the attribute information of the first postgres database corresponding to the identifier, and sends the obtained attribute information of the first postgres database to the standby management node broadcasting the DHCP DISCOVER message through a DHCP OFFER message. And when the standby management node receives the DHCP OFFER message, if the message carries the attribute information of the first postgres database, the standby management node does not process the message according to a mode specified by a DHCP protocol, but acquires the attribute information of the first postgres database from the DHCP OFFER message and compares the attribute information with the attribute information of the second postgres database corresponding to the standby management node.
And if the DHCP DISCOVER message does not contain the identifier representing the attribute information of the first postgres database corresponding to the main management node, processing the DHCPDISCOVER message according to the DHCP protocol. And when the DHCP OFFER message received by the standby management node does not contain the attribute information of the first postgres database, processing the DHCPoffer message according to the DHCP protocol.
Furthermore, in the embodiment of the present application, the standby management node may complete acquiring the attribute information of the first Postgres database corresponding to the main management node through the DHCPDISCOVER and DHCP OFFER secondary handshake with the DHCP server.
In the embodiment of the application, a first Option is newly added in a DHCP DISCOVER message so as to identify and apply for attribute information of a first postgres database corresponding to the primary management node. And adding a second Option in the DHCP OFFER message, wherein the Option carries the attribute information of the first Postgres database.
In this embodiment, an extension field in a DHCP message is used to set an identifier representing attribute information of a first postgres database corresponding to the active management node, where the identifier should include an identifier of the first postgres database.
Fig. 3 is a schematic structural diagram of a management node according to an embodiment of the present application. Referring to fig. 3, the management node 300 includes:
a main management node 301 and a standby management node 302;
the active management node 301 is configured to: periodically sending attribute information of a first postgres database corresponding to the main management node to a DHCP server;
the standby management node 302 is configured to: periodically requesting attribute information of the first postgres database from the DHCP server;
and synchronizing the data of the first postgres database to the second postgres database when the obtained attribute information of the first postgres database is determined to be different from the attribute information of the second postgres database corresponding to the first postgres database.
In an optional embodiment of the present application, the active management node 301 is specifically configured to:
and periodically detecting whether the data in the first postgres database is updated, and sending the attribute information of the first postgres database corresponding to the main management node to the DHCP server after the update is detected.
In an optional embodiment of the present application, the standby management node 302 is configured to periodically request the DHCP server for attribute information of the first postgres database by:
the standby management node regularly broadcasts a DHCP DISCOVER message, the DHCPDISCOVER message contains a representation application, the identification of the attribute information of a first postgres database corresponding to the main management node is received by the DHCP server, and the DHCP message contains the representation application, and after the identification of the attribute information of the first postgres database corresponding to the main management node, the attribute information of the first postgres database corresponding to the main management node is sent to the standby management node through DHCP PFFER messages.
In an optional embodiment of the present application, the attribute information at least includes: database data size information and metadata information.
In an optional embodiment of the present application, the standby management node 302 is configured to determine that the obtained attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node, and synchronize the data of the first postgres database with the second postgres database:
the standby management node compares the data size and the metadata information of the first postgres database with the data size and the metadata information of the second postgres database, determines that the data size of the first postgres database is different from the data size of the second postgres database, and/or the metadata information of the first postgres database is different from the metadata information of the second postgres database, and synchronizes the data of the first postgres database to the second postgres database.
Fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 4, an embodiment of the present application provides a computer device for executing the data synchronization method in fig. 1 to fig. 2, where the computer device includes a memory 1000, a processor 2000 and a computer program stored in the memory 1000 and executable on the processor 2000, where the processor 2000 implements the steps of the data synchronization method when executing the computer program.
Specifically, the memory 1000 and the processor 2000 may be general memories and processors, which are not specifically limited herein, and when the processor 2000 runs a computer program stored in the memory 2000, the data synchronization method may be executed, so as to solve the problem in the prior art that, after a primary management node and a standby management node in a big data cluster are switched once, if the current primary management node fails again, a secondary primary/standby switching fails due to a fact that a Postgres database of the standby management node is not synchronized with a Postgres database of the primary management node in time, and finally, a service cannot normally run; therefore, the embodiment of the application has the positive effect of improving the operational reliability of the big data integration management platform and can improve the user experience.
Corresponding to the data synchronization method in fig. 1 to 2, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program is executed by a processor to perform the steps of the data synchronization method.
Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, and the like, and when a computer program on the storage medium is executed, the data synchronization method can be executed, so that the problem in the prior art that, after a primary management node and a standby management node in a big data cluster are switched once, if the current primary management node fails again, a secondary primary-standby switching fails due to the fact that a Postgres database of the standby management node is not synchronized with a Postgres database of the primary management node in time, and finally, a service cannot normally run is solved; therefore, the embodiment of the application has the positive effect of improving the operational reliability of the big data integration management platform and can improve the user experience.
In the embodiments provided in the embodiments of the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In addition, functional modules in the embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.
The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application, which essentially or partly contribute to the prior art, may be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (6)

1. A data synchronization method is applied to management nodes in a big data management system, wherein the management nodes comprise a main management node and a standby management node, and the method comprises the following steps:
the main management node periodically detects whether data in a first postgres database corresponding to the main management node is updated or not, and sends attribute information of the first postgres database corresponding to the main management node to a DHCP server after the update is detected;
the standby management node periodically broadcasts a DHCP DISCOVER message, wherein the DHCP DISCOVER message comprises an identifier representing attribute information of a first postgres database corresponding to the main management node, so that after the DHCP DISCOVER message is received and the identifier is judged to be contained in the DHCP message, the DHCP DISCOVER message sends the attribute information of the first postgres database corresponding to the main management node to the standby management node through a DHCP OFFER message;
and the standby management node determines that the acquired attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node, and synchronizes the data of the first postgres database to the second postgres database.
2. The method of claim 1, wherein the attribute information comprises: data size and metadata information.
3. The method of claim 2, wherein the backup management node synchronizing the data of the first postgres database to a second postgres database when determining that the obtained attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the backup management node, comprises:
the standby management node compares the data size and the metadata information of the first postgres database with the data size and the metadata information of the second postgres database, determines that the data size of the first postgres database is different from the data size of the second postgres database, and/or the metadata information of the first postgres database is different from the metadata information of the second postgres database, and synchronizes the data of the first postgres database to the second postgres database.
4. A management node in a big data management system, comprising: a main management node and a standby management node;
the master management node is configured to: periodically detecting whether data in a first postgres database corresponding to the main management node is updated or not, and sending attribute information of the first postgres database corresponding to the main management node to a DHCP server after the data is detected to be updated;
the standby management node is configured to: broadcasting a DHCP DISCOVER message periodically, wherein the DHCP DISCOVER message contains an identifier representing attribute information of a first postgres database corresponding to the main management node, so that after the DHCP DISCOVER message is received and the DHCP DISCOVER message is judged to contain the identifier, the DHCP DISCOVER message sends the attribute information of the first postgres database corresponding to the main management node to the standby management node through a DHCP OFFER message;
and synchronizing the data of the first postgres database to the second postgres database when the obtained attribute information of the first postgres database is determined to be different from the attribute information of the second postgres database corresponding to the first postgres database.
5. The management node according to claim 4, wherein the attribute information includes at least: database data size information and metadata information.
6. The management node of claim 5, wherein the standby management node is configured to synchronize the data of the first postgres database to the second postgres database by determining that the obtained attribute information of the first postgres database is different from the attribute information of the second postgres database corresponding to the standby management node;
the standby management node compares the data size and the metadata information of the first postgres database with the data size and the metadata information of the second postgres database, determines that the data size of the first postgres database is different from the data size of the second postgres database, and/or the metadata information of the first postgres database is different from the metadata information of the second postgres database, and synchronizes the data of the first postgres database to the second postgres database.
CN201811284990.0A 2018-10-31 2018-10-31 Data synchronization method and management node Active CN109344202B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811284990.0A CN109344202B (en) 2018-10-31 2018-10-31 Data synchronization method and management node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811284990.0A CN109344202B (en) 2018-10-31 2018-10-31 Data synchronization method and management node

Publications (2)

Publication Number Publication Date
CN109344202A CN109344202A (en) 2019-02-15
CN109344202B true CN109344202B (en) 2021-04-06

Family

ID=65313169

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811284990.0A Active CN109344202B (en) 2018-10-31 2018-10-31 Data synchronization method and management node

Country Status (1)

Country Link
CN (1) CN109344202B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116781494B (en) * 2023-08-17 2024-03-26 天津南大通用数据技术股份有限公司 Main-standby switching judgment method based on existing network equipment
CN117033087B (en) * 2023-10-10 2024-01-19 武汉吧哒科技股份有限公司 Data processing method, device, storage medium and management server

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7103586B2 (en) * 2001-03-16 2006-09-05 Gravic, Inc. Collision avoidance in database replication systems
CN101436209B (en) * 2008-12-15 2011-01-05 中兴通讯股份有限公司 Method and apparatus for synchronizing multiple databases
CN102780790A (en) * 2012-07-13 2012-11-14 深圳市龙视传媒有限公司 Method and system for dynamically allocating IP (Internet Protocol) address
CN103384266B (en) * 2013-06-07 2016-12-28 曙光信息产业(北京)有限公司 A kind of Parastor200 based on file-level real-time synchronization manages node high availability method
CN105933402A (en) * 2016-04-19 2016-09-07 福建星网智慧科技股份有限公司 Method for synchronizing enterprise contacts

Also Published As

Publication number Publication date
CN109344202A (en) 2019-02-15

Similar Documents

Publication Publication Date Title
EP3490224A1 (en) Data synchronization method and system
CN106850710B (en) Data cloud storage system, client terminal, storage server and application method
US8719386B2 (en) System and method for providing configuration synchronicity
CN110536330B (en) UE migration method, device, system and storage medium
CN107404509B (en) Distributed service configuration system and information management method
US10069941B2 (en) Scalable event-based notifications
CN111259072A (en) Data synchronization method and device, electronic equipment and computer readable storage medium
CN109344202B (en) Data synchronization method and management node
US10802896B2 (en) Rest gateway for messaging
CN113347037B (en) Data center access method and device
CN112218342A (en) Method, device and system for realizing core network sub-slice disaster tolerance
CN111163173A (en) Cluster configuration method and device, server and readable storage medium
CN111526185B (en) Data downloading method, device, system and storage medium
CN107592199B (en) Data synchronization method and system
CN106487611B (en) Method and device for detecting SDN cluster split
CN114007241B (en) ZigBee system, gateway equipment thereof, gateway switching method and device
CN106533751B (en) SDN controller cluster merging method and device
EP3570169B1 (en) Method and system for processing device failure
CN108009045B (en) Method and device for processing faults of main and standby databases
CN111258795B (en) Samba cluster fault reconnection method, device, equipment and medium
CN115412974B (en) Shunting communication method, device, equipment and readable storage medium
CN109542981B (en) Data synchronization system and method, electronic device and storage medium
CN107087021B (en) Master-slave server determination method and device
CN111106966B (en) Information processing method and device, equipment and storage medium
CN109639849B (en) Address query processing method and service discovery device

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