CN113364864B - Server data synchronization method, system and storage medium - Google Patents
Server data synchronization method, system and storage medium Download PDFInfo
- Publication number
- CN113364864B CN113364864B CN202110620386.6A CN202110620386A CN113364864B CN 113364864 B CN113364864 B CN 113364864B CN 202110620386 A CN202110620386 A CN 202110620386A CN 113364864 B CN113364864 B CN 113364864B
- Authority
- CN
- China
- Prior art keywords
- synchronization
- node
- data
- server
- list
- 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
- 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/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Abstract
The invention discloses a server data synchronization method, a system and a storage medium, wherein the method comprises the following steps: the synchronization node acquires a preset synchronization list and determines a set in a MongoDB database contained in the synchronization list; the method comprises the following steps that a plurality of synchronous nodes establish data connection with a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list; and the synchronization node monitors the data change operation generated in the set and updates the changed data to the Elasticissearch server when detecting the data change operation. According to the method, the data synchronization is completed by using the plurality of synchronization nodes provided with different synchronization lists, and each synchronization node can monitor and synchronize data of different sets in the MongoDB database, so that the throughput of the whole data synchronization is effectively improved, and the problem that data synchronization is difficult to efficiently perform by using a single synchronization device can be effectively solved.
Description
Technical Field
The present invention relates to the field of servers, and in particular, to a server data synchronization method, system and storage medium.
Background
Elasticsearch is a distributed search and data analysis engine that typically employs MongoDB as a back-end database for storing data. However, the performance of the Elasticsearch is affected by the data synchronization speed of the mongoDB database, and if the mongoDB database cannot synchronize data to the Elasticsearch server in time, the searching and data analysis capability of the Elasticsearch server is limited, so that the data synchronization between the mongoDB database and the Elasticsearch server is an important problem in the field.
In the related art, data synchronization between the MongoDB database and the Elasticsearch server is performed by a single synchronization device, and the synchronization device performs data synchronization by monitoring data change conditions of the sets in the MongoDB database. When a large amount of data exists in the MongoDB database or the data change condition in the set is large, the method is difficult to efficiently synchronize the data and cannot ensure the data throughput.
Disclosure of Invention
The invention aims to provide a server data synchronization method, a server data synchronization system and a storage medium, wherein a plurality of synchronization nodes can be used for completing data synchronization, each synchronization node can monitor and synchronize data of different sets in a MongoDB database, the throughput of the whole data synchronization is further effectively improved, and the problem that the data synchronization is difficult to efficiently perform by using a single synchronization device can be effectively solved.
In order to solve the above technical problem, the present invention provides a server data synchronization method, including:
a synchronization node acquires a preset synchronization list and determines a set in a MongoDB database contained in the synchronization list; the method comprises the following steps that data connection is established between a plurality of synchronous nodes and a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list;
and the synchronization node monitors the data change operation generated in the set and updates the changed data to the Elasticissearch server when detecting the data change operation.
Optionally, when the synchronization node includes a stream processing module, a hash distribution module, and a local fragmentation module, the synchronization node monitors a data change operation occurring in the set, and updates changed data to the Elasticsearch server when detecting that the data change operation occurs, including:
the stream processing module monitors the data change operation and sends the changed data to the hash distribution module when the data change operation is determined to occur;
the Hash distribution module calculates the processing number of the data processed by each local fragmentation module according to the number of the received data and the fragmentation number of the local fragmentation module, and distributes the data to the local fragmentation modules according to the processing number;
the local fragmentation module determines field information of received data, determines a mapping relation between the field information and field information of an Elasticissearch server, finally calls a data updating interface of the Elasticissearch server, and updates the data to the Elasticissearch server according to the mapping relation.
Optionally, after updating the data to the Elasticsearch server according to the mapping relationship, the method further includes:
and the local fragmentation module acquires the updating progress through the data updating interface and saves the updating progress in a progress storage area.
Optionally, before the synchronization node acquires the preset synchronization list, the method further includes:
the main node acquires the collection number of all the collections in the MongoDB database and the node number of the synchronous nodes, and calculates the collection monitoring amount of each synchronous node by using the collection number and the node number;
and the master node writes the sets required to be monitored by the synchronization nodes into a synchronization list according to the set monitoring amount and sends the synchronization list to the corresponding synchronization nodes.
Optionally, after issuing the synchronization list to the corresponding synchronization node, the method further includes:
when the main node detects the occurrence of a capacity expansion event, the main node creates the synchronization list for the newly added synchronization node, and updates the set monitoring amount by using the set amount and the updated node amount;
and the master node updates the corresponding synchronization list according to the updated set monitoring amount so that the number of sets contained in the updated synchronization list is less than or equal to the updated set monitoring amount, and issues the updated synchronization list to the corresponding synchronization node.
Optionally, after issuing the synchronization list to the corresponding synchronization node, the method further includes:
when the master node detects that a capacity shrinkage event occurs, setting a synchronization list corresponding to a synchronization node to be removed as a list to be removed, and updating a set in the list to be removed to other synchronization lists;
and the master node removes the synchronization node to be removed and the list to be removed, and issues the updated synchronization list to the corresponding synchronization node.
Optionally, before the master node obtains the number of sets of all sets in the MongoDB database and the number of nodes of the synchronization node, the method further includes:
after the synchronization node is started, sending start time to a Zookeeper cluster middleware, and judging whether the master node is recorded in the Zookeeper cluster middleware;
if so, the synchronization node monitors the main node through the Zookeeper cluster middleware to receive the synchronization list sent by the main node;
if not, the synchronization node sends the device information of the synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware utilizes the device information to set the synchronization node as the master node;
and after the synchronous node completes the main node setting, executing the step of acquiring the collection number of all the collections in the MongoDB database and the node number of the synchronous node.
Optionally, after issuing the synchronization list to the corresponding synchronization node, the method further includes:
the Zookeeper cluster middleware sends heartbeat data to the main node, so that the main node returns receipt data to the Zookeeper cluster middleware;
if the Zookeeper cluster middleware does not receive the receipt data, sending a main node offline notification to all the synchronous nodes;
after receiving the master node offline notification, the first synchronization node acquires the first starting time of the first synchronization node and the second starting time of other synchronization nodes from the Zookeeper cluster middleware, and judges whether the second starting time later than the first starting time exists or not;
if so, after waiting for a preset time period, the first synchronization node judges whether the main node is recorded in the Zookeeper cluster middleware;
if the main node is recorded, the first synchronization node monitors the main node through the Zookeeper cluster middleware;
if the master node is not recorded, the first synchronization node sends the device information of the first synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the first synchronization node as the master node by using the device information of the first synchronization node;
if not, the first synchronization node sends the device information of the first synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware utilizes the device information to set the first synchronization node as the master node.
The invention also provides a server data synchronization system, comprising: a synchronization node, a MongoDB database and an Elasticsearch server, wherein,
the MongoDB database is used for storing data required by the Elasticissearch server;
the synchronization node is used for acquiring a preset synchronization list and determining a set in a MongoDB database contained in the synchronization list; the method comprises the following steps that a plurality of synchronous nodes establish data connection with a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list; the synchronization node monitors data change operation occurring in the set, and updates changed data to the Elasticissearch server after detecting that the data change operation occurs;
and the Elasticissearch server is used for receiving the data sent by the synchronous node.
The present invention also provides a storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the server data synchronization method as described above.
The invention provides a server data synchronization method, which comprises the following steps: a synchronization node acquires a preset synchronization list and determines a set in a MongoDB database contained in the synchronization list; the method comprises the following steps that data connection is established between a plurality of synchronous nodes and a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list; and the synchronization node monitors the data change operation generated in the set and updates the changed data to the Elasticissearch server when detecting the data change operation.
Therefore, the method uses a plurality of synchronous nodes to complete data synchronization between the MongoDB database and the elastic search server, and each synchronous node is provided with different synchronous lists, so that different sets in the MongoDB database can be monitored, the synchronous work of a single synchronous device in the related technology can be effectively distributed to the plurality of synchronous nodes, each synchronous node can be ensured to have a proper monitoring amount, and the synchronous nodes can still efficiently perform data synchronization under the condition that the number of sets in the MongoDB database is large or the data change condition in the sets is large, and the condition that the data synchronization efficiency is difficult to ensure by adopting a single synchronous device in the related technology is avoided; meanwhile, a plurality of synchronous nodes in the method can monitor data change operation in the set at the same time, and when the data change operation is determined to occur, the changed data is rapidly updated to the elastic search server, so that the data throughput can be effectively improved, and the problem that data synchronization is difficult to perform efficiently by adopting a single synchronous device in the related technology can be effectively solved. The invention also provides a server data synchronization system and a storage medium, which have the beneficial effects.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a server data synchronization method according to an embodiment of the present invention;
fig. 2 is a block diagram of a hardware framework to which a server data synchronization method according to an embodiment of the present invention is applicable;
FIG. 3 is a flowchart of another server data synchronization method according to an embodiment of the present invention;
fig. 4a is a block diagram of a server data synchronization system according to an embodiment of the present invention;
fig. 4b is a block diagram of a synchronization node according to an embodiment of the present invention;
FIG. 4c is a block diagram of another server data synchronization system according to an embodiment of the present invention;
fig. 4d is a block diagram of another server data synchronization system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. 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 invention.
In the related art, data synchronization between the MongoDB database and the Elasticsearch server is performed by a single synchronization device, and the synchronization device performs data synchronization by monitoring data change conditions of the sets in the MongoDB database. When a large amount of data exists in the MongoDB database or the data change condition in the set is large, the method is difficult to efficiently synchronize the data and cannot ensure the data throughput. The MongoDB database is a database based on distributed file storage. In view of this, the present invention provides a server data synchronization method, which can use multiple synchronization nodes to complete data synchronization, and each synchronization node can monitor and synchronize data of different sets in a montogodb database, thereby effectively improving throughput of overall data synchronization, and effectively solving the problem that it is difficult for a single synchronization device to efficiently synchronize data. Referring to fig. 1, fig. 1 is a flowchart of a server data synchronization method according to an embodiment of the present invention, where the method includes:
s101, a synchronization node acquires a preset synchronization list and determines a set in a MongoDB database contained in the synchronization list; the method comprises the steps that a plurality of synchronization nodes establish data connection with a MongoDB database and an Elasticissearch server, and each synchronization node corresponds to a different synchronization list.
In an embodiment of the present invention, the synchronization node is an independent device independent of the mongoDB database and the elastic search service, and is used for synchronizing data between the MongoDB database and the elastic search server. Referring to fig. 2, fig. 2 is a structural block diagram of a hardware framework to which the server data synchronization method provided by the embodiment of the present invention is applied, and it can be seen that a plurality of synchronization nodes (synchronization node 1 to synchronization node n) are connected in parallel between a MongoDB database and an Elasticsearch server. It should be noted that, the embodiment of the present invention does not limit the specific hardware structure of the synchronization node, as long as the embodiment of the present invention can complete the server data synchronization method provided by the embodiment of the present invention. The embodiment of the invention also does not limit the number of the synchronous nodes and can be set according to the actual application requirements. Considering that the MongoDB has the node access number limit to the monitoring node, when the synchronization node is set, the number of the synchronization node is less than or equal to the node access number limit of the MongoDB.
Further, in the embodiment of the present invention, each synchronization node stores a preset synchronization list, and the synchronization list stores a montgodb set that the node needs to monitor, where the montgodb set (Collection) is a data type of the montgodb data. Each synchronization node corresponds to different synchronization lists, and then each synchronization node monitors different sets in the MongoDB, so that not only can all the synchronization nodes be ensured to effectively monitor all the sets in the MongoDB, but also a set monitoring task can be divided into a plurality of synchronization nodes, each synchronization node is ensured to monitor with proper workload, and further the synchronization nodes are ensured to work efficiently. It should be noted that the embodiment of the present invention does not limit the specific form of the synchronization list, as long as the synchronization list can store the information of the montgodb set, and the synchronization list can be adjusted according to the actual application requirements; the embodiment of the invention also does not limit the number of MongoDB sets contained in each synchronization list, and can be adjusted according to the actual application requirements. Of course, in order to ensure the workload of each synchronization node is balanced, when the synchronization list is set, each synchronization node may be load balanced, and the aggregate snooping amount of each synchronization node is ensured to be the same or similar (i.e. the difference between the snooping amounts of the synchronization nodes is within the preset range). The embodiment of the present invention does not limit the specific steps of load balancing, as long as it can ensure that each synchronization node can work with the same or similar snooping amount.
S102, monitoring data change operation in the set by the synchronization node, and updating the changed data to an elastic search server when detecting that the data change operation occurs.
In the embodiment of the present invention, since the MongoDB database is used to store the data required by the Elasticsearch server, when a data change occurs in the MongoDB database, it is necessary to synchronize the changed data to the Elasticsearch server. If the synchronization node determines that a data change operation has occurred, the changed data needs to be updated to the Elasticsearch server synchronously to ensure data synchronization.
It should be noted that the embodiment of the present invention does not limit the specific implementation manner of the synchronization node to determine whether the data change operation occurs, and reference may be made to the related art of the MongoDB Watch, where the MongoDB Watch provides a change data monitoring function for the MongoDB.
Further, when it is determined that a data change operation occurs, the synchronization node needs to write the changed data into the Elasticsearch server. It will be appreciated that the synchronization node first needs to pull the changed data out of the MongoDB database. The embodiment of the invention does not limit the specific implementation mode of data pulling, and can refer to the related technology of MongoDB Change Stream, which is a mode for MongoDB to issue data Change to an application. Furthermore, because the MongoDB Change Stream performs the function of pulling the changed data by adopting a synchronous execution process, which leads to the reduction of the data pulling efficiency, in the embodiment of the present invention, the monitoring and the changed data pulling of the MongoDB Change Stream can be changed into asynchronous execution, that is, the MongoDB Change Stream asynchronously initiates the next data pulling when determining that the data pulled from the MongoDB at this time is synchronously processed with the elastic search server.
Furthermore, the embodiment of the present invention does not limit whether the synchronization node can obtain a plurality of local fragmentation modules by means of internal fragmentation, and divide the update operation of the changed data into the local fragmentation modules for parallel execution, and if the set monitoring amount of each synchronization node is small, the local fragmentation modules do not need to be set, that is, the changed data is updated to the elastic search server according to the acquisition sequence of the changed data; if the collection monitoring amount of each synchronization node is large, local fragmentation modules can be arranged, and then after the changed data are determined, the data need to be divided into each local fragmentation module and the local fragmentation modules perform parallel updating. In view of the fact that there are many sets in the MongoDB database, that is, the synchronization node may need to monitor multiple sets at the same time, and at this time, if a data update mode according to the acquisition order of the changed data is adopted, data is accumulated, and the data update speed is affected, in this embodiment of the present invention, a local fragmentation module may be adopted to update the changed data in parallel, in other words, the synchronization node may obtain multiple local fragmentation modules through an internal fragmentation mode, and divide the changed data write operation into the local fragmentation modules to be executed in parallel. It should be noted that, the embodiment of the present invention does not limit the number of local fragmentation modules, and may be set according to actual application requirements; the embodiment of the invention also does not limit the maximum number of the changeable data which can be processed by each local fragment module, and can be set according to the actual application; the embodiment of the present invention also does not limit the specific fragmentation mode for obtaining the local fragmentation module, and may refer to the related technologies of hash fragmentation, for example, hash modeling, virtual bucket, and consistent hash modes may be adopted. Considering that the hash modulus method is simple and easy to implement, the hash modulus method can be adopted for fragmentation in the embodiment of the invention. Further, it can be understood that, when the changed data is distributed to each local fragmentation module, a hash modeling method may also be used to obtain the changed data corresponding to each local fragmentation module, and specifically, reference may be made to the related technology of the hash modeling method.
In a possible case, when a synchronization node includes a stream processing module, a hash distribution module and a local fragmentation module, the synchronization node monitors a data change operation occurring in a collection, and updates changed data to an Elasticsearch server when detecting that the data change operation occurs, including:
step 11: the stream processing module monitors data change operation and sends the changed data to the hash distribution module when determining that the data change operation occurs.
The Stream processing module may be implemented using the above-described MongoDB Watch and MongoDB Change Stream, and specific definition descriptions may refer to the above description.
Step 12: the Hash distribution module calculates the processing number of the data processed by each local fragmentation module according to the number of the received data and the fragmentation number of the local fragmentation module, and distributes the data to the local fragmentation module according to the processing number.
The Hash distribution module adopts a Hash modular method to distribute data. In the embodiment of the invention, in order to ensure load balance of the local fragmentation modules, the average processing number of each local fragmentation module is calculated according to the obtained data number and the fragmentation number, and then data are distributed to the local fragmentation modules according to the processing number.
Step 13: and the local fragmentation module determines the field information of the received data, determines the mapping relation between the field information and the field information of the Elasticissearch server, finally calls a data updating interface of the Elasticissearch server, and updates the data to the Elasticissearch server according to the mapping relation.
It can be understood that mongoDB and elastic search are two heterogeneous databases, so that the change data needs to be synchronized to the elastic search server according to the field mapping relationship between MongoDB and elastic search. It should be noted that, the embodiment of the present invention does not limit the specific form of the field mapping relationship, and may refer to the related technologies of MongoDB and elastic search and set in combination with the specific application requirements. It will also be appreciated that the altered data may be synchronized to the Elasticsearch server using the Elasticsearch server's data update interface, which may also refer to Elasticsearch's related art.
Furthermore, it should be noted that the embodiment of the present invention does not limit whether the local fragment needs to store the data update schedule obtained by callback from the data update interface, and if the amount of data synchronized each time is small, or it can be ensured that the synchronization node is not offline, the data update schedule does not need to be stored; when the data amount of each synchronization is large or the synchronization node may be offline, the data update progress may be saved. In the embodiment of the present invention, in order to ensure that the synchronization node or the local fragment module can continue to transmit at the breakpoint when coming online next time, the data update progress can be saved in consideration of the fact that the synchronization node or the local fragment module may be offline. It should be noted that the embodiment of the present invention does not limit the specific implementation manner of obtaining the data update progress from the Elasticsearch data update interface callback, and reference may be made to the related technology of Elasticsearch.
In a possible case, after updating the data to the Elasticsearch server according to the mapping relationship, the method further includes:
step 21: and the local fragmentation module acquires the updating progress through the data updating interface and saves the updating progress in a progress storage area.
The embodiment of the invention does not limit the specific progress storage area, can be the cache of the local fragmentation module, can also be an independent database, and can be set according to the actual application requirements. The embodiment of the invention also does not limit the progress storage area to only store the updating progress of the single local fragmentation module or store the updating progress of all the local fragmentation modules. In order to ensure the overall working reliability of the synchronization node, in the embodiment of the present invention, the progress storage area may store the update progress of all local fragmentation modules.
Finally, it can be understood that the synchronization node should set a synchronization list before use, and the embodiment of the present invention does not limit the configuration manner of the synchronization node, for example, the synchronization list may be manually input, and the master node may also be used to perform unified node management. In the embodiment of the invention, in order to improve the deployment efficiency, the master node can be used for carrying out unified management on the synchronous nodes, namely the master node can issue the synchronous list to the synchronous nodes. It will be appreciated that the master node and the synchronization nodes form a synchronization cluster. Further, the master node in the embodiment of the present invention may be an independent management node without a function of the synchronization node, or may be a management node obtained by switching functions of the synchronization node. In the embodiment of the present invention, in order to ensure that the synchronization cluster stably operates, that is, when the master node stops serving, the master node may be obtained by performing function switching on another management node, and the master node may be a management node obtained by performing function switching on the synchronization node. In other words, any synchronization node in the synchronization cluster can perform function switching to obtain the master node.
The server data synchronization method is described below with reference to a specific flowchart. Referring to fig. 3, fig. 3 is a flowchart of another server Data synchronization method according to an embodiment of the present invention, where an asynchronous Stream is used to asynchronously obtain changed Data, the read of Next Data is started after the currently obtained Data (Data) is processed by a Hash module, and a Watch is used to monitor a Data change operation, where the Stream processing module is composed of the asynchronous Stream and the Watch. Hash denotes a Hash fragmentation module, which is used to distribute data to local fragmentation modules. The local fragmentation module consists of a Filter and an Option together, wherein the Option is used for calling a data updating interface of the Elasticissearch server and writing changed data into the Elasticissearch server, and the Filter represents a progress Filter and is used for receiving the data updating progress of the local fragmentation module returned by the data updating interface and storing the progress to the progress for storage. The asynchronous Stream, Watch, Hash, Filter and options 1-4 are all deployed in the same synchronous node.
Based on the embodiment, the method uses a plurality of synchronization nodes to complete data synchronization between the MongoDB database and the Elasticissearch server, and each synchronization node is provided with different synchronization lists, so that different sets in the MongoDB database can be monitored, the synchronization work of a single synchronization device in the related technology can be effectively distributed to the plurality of synchronization nodes, each synchronization node can be ensured to have a proper monitoring amount, and the synchronization nodes can still efficiently perform data synchronization under the conditions that the number of sets in the MongoDB database is large or the data change condition in the sets is large, and the condition that the data synchronization efficiency is difficult to ensure by adopting a single synchronization device in the related technology is avoided; meanwhile, because the plurality of synchronization nodes in the method can monitor the data change operation in the set at the same time, and quickly update the changed data to the elastic search server when the data change operation is determined to occur, the data throughput can be effectively improved, and the problem that the data synchronization is difficult to be efficiently performed by adopting a single synchronization device in the related technology can be effectively solved.
Based on the above embodiments, the following describes the configuration management process of the synchronization node by the master node. In a possible case, before the synchronization node acquires the preset synchronization list, the method may further include:
s201, the main node acquires the collection number of all the collections in the MongoDB database and the node number of the synchronous nodes, and calculates the collection monitoring amount of each synchronous node by using the collection number and the node number.
For the definition description of the master node, reference may be made to the above embodiments, which are not repeated herein. In order to ensure that each synchronization node works with a balanced aggregate snooping amount, in the embodiment of the present invention, after acquiring the number of aggregates in the MongoDB database, the master node needs to calculate the average aggregate snooping amount of each synchronization node. It is understood that the aggregate snoop amount is an integer. If the main node generates remainder when calculating the set monitoring amount, the redundant monitoring amount can be averagely distributed to the synchronous nodes.
It should be noted that the embodiment of the present invention does not limit the specific way in which the master node obtains the number of sets of the MongoDB database, and reference may be made to the related art of the MongoDB.
S202, the main node writes the sets to be monitored by the synchronization nodes into the synchronization list according to the set monitoring amount, and issues the synchronization list to the corresponding synchronization nodes.
Further, the embodiment of the present invention does not limit the number of the synchronization nodes to be changeable, in other words, the embodiment of the present invention does not limit whether the capacity expansion or the capacity reduction of the synchronization cluster occurs, and when the number of the synchronization nodes can meet the application requirement, the synchronization cluster may not need to perform the capacity expansion or the capacity reduction; when the number of the synchronous nodes is difficult to meet the application requirement, and the situation of insufficient or excessive computing resources may occur, the synchronous cluster may also perform capacity expansion and capacity reduction. In the embodiment of the invention, in order to meet various application requirements of users of the synchronous cluster, the synchronous cluster can be subjected to capacity expansion or capacity reduction, and the main node can also be subjected to load balancing again when capacity expansion or capacity reduction events occur, so that each synchronous node which normally works can be ensured to work with the same or similar set monitoring amount.
In one possible case, after issuing the synchronization list to the corresponding synchronization node, the method further includes:
step 31: when detecting the occurrence of a capacity expansion event, the master node creates a synchronization list for the newly added synchronization node, and updates the set monitoring volume by using the set number and the updated node number.
Step 32: and the master node updates the corresponding synchronization list according to the updated set monitoring amount so that the number of sets contained in the updated synchronization list is less than or equal to the updated set monitoring amount, and issues the updated synchronization list to the corresponding synchronization node.
It can be understood that, when the synchronous cluster is subjected to capacity expansion, the set snooping amount should be updated at this time, the synchronous lists corresponding to the set snooping amount which is actually greater than the updated set snooping amount are determined, and redundant sets in the synchronous lists are moved to the synchronous list of the newly-added synchronous node.
In one possible case, after issuing the synchronization list to the corresponding synchronization node, the method further includes:
step 41: when detecting that a capacity shrinkage event occurs, the master node sets a synchronization list corresponding to a synchronization node to be removed as a list to be removed, and updates a set in the list to be removed to other synchronization lists;
step 42: and the master node removes the synchronization node to be removed and the list to be removed, and issues the updated synchronization list to the corresponding synchronization node.
It can be understood that when the capacity reduction occurs in the synchronization cluster, the sets in the synchronization list to be removed need to be evenly distributed to other synchronization lists at this time, so as to ensure that the rest of the synchronization nodes can still continue to listen to the MongoDB database.
Further, in order to further improve the management efficiency of the synchronization cluster, in the embodiment of the present invention, cluster management may be performed by using a Zookeeper cluster middleware, where the Zookeeper is a distributed application coordination service. The Zookeeper cluster middleware can detect the survival condition of the main node and maintain the communication with the main node through a heartbeat mechanism. And when the Zookeeper determines that the communication between the Zookeeper and the main node is lost, namely the main node is offline, sending a main node offline notification to the synchronous node so that the synchronous node competes for a new main node.
The embodiment of the invention does not limit the specific heartbeat mechanism, for example, the Zookeeper cluster middleware periodically sends heartbeat data to the master node, receives receipt data of the master node, and determines that the master node is offline when the receipt data of the master node cannot be received; certainly, the Zookeeper cluster middleware may also periodically receive heartbeat data of the master node, and determine that the master node is offline when the heartbeat data of the master node cannot be received. In order to ensure that the working condition of the Zookeeper cluster middleware does not affect the synchronous cluster, in the embodiment of the present invention, the heartbeat mechanism may be that the Zookeeper cluster middleware sends heartbeat data to the master node and receives receipt data of the master node. Of course, the Zookeeper cluster middleware can also use the heartbeat mechanism to maintain communication with the synchronization node to ensure the survival of the synchronization node. It should be noted that, the embodiment of the present invention does not limit the sending period of the heartbeat data, and can be set according to the actual application requirements.
The embodiment of the present invention also does not limit the way in which the synchronization node contends for the master node, for example, the master node may be selected in a cluster node election way, or the synchronization node may send the device information to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the synchronization node corresponding to the device information received first as the master node. Considering that the cluster node election is relatively complicated, the master node contending process in the embodiment of the present invention may be: and the synchronization node sends the equipment information to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the synchronization node corresponding to the first received equipment information as a main node. Of course, it may also be possible to set a specific synchronization node to preferentially contend for the master node, and other synchronization nodes wait for the synchronization node to complete the master node configuration, and continue to contend for the master node if the synchronization node configuration fails. The embodiment of the present invention does not limit the manner of setting the specific synchronization node, for example, setting a sequence number for the synchronization node, and setting a specific sequence number for a synchronization node to preferentially contend for the master node, or recording the start time of the synchronization node and preferentially allowing the synchronization node with the latest start time to contend for the master node.
In a possible case, before the master node obtains the collection number of all the collections in the MongoDB database and the node number of the synchronization node, the method further includes:
step 51: after the synchronization node is started, sending start time to the Zookeeper cluster middleware, and judging whether a master node is recorded in the Zookeeper cluster middleware; if yes, go to step 52; if not, go to step 53.
Step 52: the synchronization node monitors the main node through the Zookeeper cluster middleware to receive the synchronization list sent by the main node.
Step 53: and the step node sends the equipment information of the synchronization node to the Zookeeper cluster middleware so that the Zookeeper cluster middleware sets the synchronization node as a main node by using the equipment information.
Step 54: and after the synchronous nodes finish the setting of the main nodes, executing the step of acquiring the collection number of all the collections in the MongoDB database and the node number of the synchronous nodes.
In one possible case, after issuing the synchronization list to the corresponding synchronization node, the method further includes:
step 61: and the Zookeeper cluster middleware sends heartbeat data to the main node, so that the main node returns receipt data to the Zookeeper cluster middleware.
Step 62: and if the Zookeeper cluster middleware does not receive the receipt data, sending a main node offline notification to all the synchronous nodes.
And step 63: after receiving the main node offline notification, the first synchronization node acquires the first starting time of the first synchronization node and the second starting time of other synchronization nodes from the Zookeeper cluster middleware, and judges whether the second starting time later than the first starting time exists or not; if yes, go to step 64; if not, go to step 67.
Step 64: after waiting for a preset time period, the first synchronization node judges whether a main node is recorded in the Zookeeper cluster middleware; if yes, go to step 65; if not, go to step 66.
Step 65: and the first synchronization node monitors the main node through the Zookeeper cluster middleware.
And step 66: and the first synchronization node sends the equipment information of the first synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware utilizes the equipment information of the first synchronization node to set the first synchronization node as a main node.
It can be understood that, after the first synchronization node is set as the master node, the data synchronization process cannot be continued, and at this time, the capacity reduction process may be performed on the first synchronization node, that is, the set in the synchronization list corresponding to the first synchronization node is allocated to another synchronization list.
Step 67: and the first synchronization node sends the equipment information of the first synchronization node to the Zookeeper cluster middleware so that the Zookeeper cluster middleware utilizes the equipment information to set the first synchronization node as a main node.
Based on the embodiment, the main node in the method can automatically perform load balancing on the sets monitored by the synchronization nodes, ensure that the synchronization nodes perform data synchronization by using the same or similar set monitoring amount, and further ensure that the synchronization nodes maintain higher working efficiency to perform data synchronization.
In the following, the server data synchronization system and the storage medium provided by the embodiments of the present invention are introduced, and the server data synchronization system and the storage medium described below and the server data synchronization method described above may be referred to correspondingly.
Referring to fig. 4a, fig. 4a is a block diagram of a server data synchronization system according to an embodiment of the present invention, where the system may include: a synchronization node 410, a MongoDB database 420, and an Elasticsearch server 430, wherein,
a MongoDB database 420 for storing data required by the Elasticissearch server;
the synchronization node 410 is configured to obtain a preset synchronization list, and determine a set in the montogdb database included in the synchronization list; the method comprises the following steps that a plurality of synchronous nodes establish data connection with a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list; the synchronization node monitors data change operation in the set and updates the changed data to an Elasticissearch server after detecting the occurrence of the data change operation;
and the Elasticsearch server 430 is configured to receive data sent by the synchronization node.
Optionally, referring to fig. 4b, fig. 4b is a block diagram of a synchronization node according to an embodiment of the present invention, where the synchronization node may include a stream processing module 411, a hash distribution module 412, and a local fragmentation module 413, where,
the stream processing module 411 is configured to monitor a data change operation, and send changed data to the hash distribution module when it is determined that the data change operation occurs;
the hash distribution module 412 is configured to calculate the number of processed data pieces of each local fragmentation module according to the number of received data pieces and the number of fragments of the local fragmentation module, and distribute the data to the local fragmentation modules according to the number of processed data pieces;
the local fragmentation module 413 is configured to determine field information of the received data, determine a mapping relationship between the field information and the field information of the Elasticsearch server, finally call a data update interface of the Elasticsearch server 430, and update the data to the Elasticsearch server 430 according to the mapping relationship.
Optionally, the local fragmentation module 413 is further configured to obtain an update progress through the data update interface, and save the update progress in the progress storage area.
Optionally, referring to fig. 4c, fig. 4c is a block diagram of another server data synchronization system according to an embodiment of the present invention, which may further include a master node 440, wherein,
the master node 440 is configured to obtain the number of sets of all sets in the MongoDB database 420 and the number of nodes of the synchronization node 410, and calculate the set monitoring amount of each synchronization node 410 by using the number of sets and the number of nodes; and writing the sets to be monitored by the synchronization nodes 410 into the synchronization list according to the set monitoring amount, and issuing the synchronization list to the corresponding synchronization nodes 410.
Optionally, the master node 440 is further configured to create a synchronization list for the newly added synchronization node 410 when an expansion event is detected to occur, and update the set monitoring amount by using the set amount and the updated node amount; and updating the corresponding synchronization list according to the updated set monitoring amount so that the number of sets included in the updated synchronization list is less than or equal to the updated set monitoring amount, and sending the updated synchronization list to the corresponding synchronization node 410.
Optionally, the master node 440 is further configured to set a synchronization list corresponding to the synchronization node 410 to be removed as a list to be removed when detecting that a capacity reduction event occurs, and update a set in the list to be removed to another synchronization list; the synchronization node 410 to be removed and the list to be removed are removed, and the updated synchronization list is sent to the corresponding synchronization node 410.
Optionally, referring to fig. 4d, fig. 4d is a block diagram of a structure of another server data synchronization system provided in the embodiment of the present invention, where the system may further include: zookeeper cluster middleware 450, wherein,
the synchronization node 410 is further configured to send a start time to the Zookeeper cluster middle 450 after starting, and determine whether the master node 440 is recorded in the Zookeeper cluster middle; if so, the synchronization node monitors the master node 440 through the Zookeeper cluster middleware to receive the synchronization list issued by the master node 440; if not, the synchronization node sends the device information of the synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the synchronization node as the master node 440 by using the device information; after the main node setting is finished, the step of acquiring the collection number of all the collections in the MongoDB database and the node number of the synchronous nodes is executed;
the Zookeeper cluster middleware 450 is configured to record the start time sent by the synchronization node 410 and the device information of the master node 440.
Optionally, the Zookeeper cluster middleware 450 is further configured to send heartbeat data to the master node 440, so that the master node 440 returns receipt data to the Zookeeper cluster middleware 450; if the receipt data is not received, sending a main node offline notification to all the synchronous nodes;
the synchronization node 410 is further configured to, after receiving the master node offline notification, obtain the first start time and the second start times of other synchronization nodes from the Zookeeper cluster middleware 450, and determine whether a second start time later than the first start time exists; if yes, after waiting for a preset time period, judging whether the Zookeeper cluster middleware 450 records the master node 440; if the master node 440 is recorded, monitoring the master node 440 through the Zookeeper cluster middleware 450; if the master node 440 is not recorded, sending the device information of the synchronization node 410 to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the synchronization node 410 as the master node by using the device information of the synchronization node 410; if not, the device information of the synchronization node 410 is sent to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the synchronization node 410 as the master node 440 by using the device information.
The embodiment of the present invention further provides a storage medium, where a computer program is stored on the storage medium, and when the computer program is executed by a processor, the steps of the server data synchronization method according to any of the above embodiments are implemented.
Since the embodiment of the storage medium portion and the embodiment of the server data synchronization method portion correspond to each other, please refer to the description of the embodiment of the server data synchronization method portion for the embodiment of the storage medium portion, which is not repeated here.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The server data synchronization method, system and storage medium provided by the present invention are described in detail above. The principles and embodiments of the present invention have been described herein using specific examples, which are presented only to assist in understanding the method and its core concepts of the present invention. It should be noted that, for those skilled in the art, without departing from the principle of the present invention, it is possible to make various improvements and modifications to the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Claims (9)
1. A server data synchronization method, comprising:
a synchronization node acquires a preset synchronization list and determines a set in a MongoDB database contained in the synchronization list; the method comprises the following steps that data connection is established between a plurality of synchronous nodes and a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list;
the synchronization node monitors data change operation occurring in the set and updates changed data to the Elasticissearch server when detecting that the data change operation occurs;
when the synchronization node comprises a stream processing module, a hash distribution module and a local fragmentation module, the synchronization node monitors data change operation occurring in the set, and updates changed data to the Elasticsearch server when detecting that the data change operation occurs, including:
the stream processing module monitors the data change operation and sends the changed data to the hash distribution module when the data change operation is determined to occur;
the Hash distribution module calculates the processing number of the data processed by each local fragmentation module according to the number of the received data and the fragmentation number of the local fragmentation module, and distributes the data to the local fragmentation modules according to the processing number;
the local fragmentation module determines field information of received data, determines a mapping relation between the field information and field information of an Elasticissearch server, finally calls a data updating interface of the Elasticissearch server, and updates the data to the Elasticissearch server according to the mapping relation.
2. The server data synchronization method according to claim 1, further comprising, after updating the data to the Elasticsearch server according to the mapping relationship:
and the local fragmentation module acquires the updating progress through the data updating interface and saves the updating progress in a progress storage area.
3. The server data synchronization method according to any one of claims 1 to 2, further comprising, before the synchronization node acquires the preset synchronization list:
the main node obtains the number of sets of all sets in the MongoDB database and the number of nodes of the synchronous nodes, and calculates the set monitoring amount of each synchronous node by using the number of sets and the number of nodes;
and the master node writes the sets required to be monitored by the synchronization nodes into a synchronization list according to the set monitoring amount and sends the synchronization list to the corresponding synchronization nodes.
4. The method for synchronizing server data according to claim 3, further comprising, after sending the synchronization list to the corresponding synchronization node:
when detecting the occurrence of a capacity expansion event, the master node creates the synchronization list for the newly added synchronization node, and updates the set monitoring amount by using the set amount and the updated node amount;
and the master node updates the corresponding synchronization list according to the updated set monitoring amount so that the number of sets contained in the updated synchronization list is less than or equal to the updated set monitoring amount, and issues the updated synchronization list to the corresponding synchronization node.
5. The server data synchronization method of claim 3, after sending the synchronization list to the corresponding synchronization node, further comprising:
when the master node detects that a capacity shrinkage event occurs, setting a synchronization list corresponding to a synchronization node to be removed as a list to be removed, and updating a set in the list to be removed to other synchronization lists;
and the master node removes the synchronization node to be removed and the list to be removed, and issues the updated synchronization list to the corresponding synchronization node.
6. The server data synchronization method according to claim 3, wherein before the master node obtains the number of sets of all sets in the MongoDB database and the number of nodes of the synchronization node, the method further comprises:
after the synchronization node is started, sending start time to a Zookeeper cluster middleware, and judging whether the master node is recorded in the Zookeeper cluster middleware;
if so, the synchronization node monitors the master node through the Zookeeper cluster middleware to receive the synchronization list issued by the master node;
if not, the synchronization node sends the device information of the synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware utilizes the device information to set the synchronization node as the master node;
and after the synchronous node completes the main node setting, executing the step of acquiring the collection number of all the collections in the MongoDB database and the node number of the synchronous node.
7. The method for synchronizing server data according to claim 6, further comprising, after sending the synchronization list to the corresponding synchronization node:
the Zookeeper cluster middleware sends heartbeat data to the main node, so that the main node returns receipt data to the Zookeeper cluster middleware;
if the Zookeeper cluster middleware does not receive the receipt data, sending a main node offline notification to all the synchronous nodes;
after receiving the master node offline notification, the first synchronization node acquires the first starting time of the first synchronization node and the second starting time of other synchronization nodes from the Zookeeper cluster middleware, and judges whether the second starting time later than the first starting time exists or not;
if so, after waiting for a preset time period, the first synchronization node judges whether the main node is recorded in the Zookeeper cluster middleware;
if the main node is recorded, the first synchronization node monitors the main node through the Zookeeper cluster middleware;
if the master node is not recorded, the first synchronization node sends the device information of the first synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware sets the first synchronization node as the master node by using the device information of the first synchronization node;
if not, the first synchronization node sends the device information of the first synchronization node to the Zookeeper cluster middleware, so that the Zookeeper cluster middleware utilizes the device information to set the first synchronization node as the master node.
8. A server data synchronization system, comprising: a synchronization node, a MongoDB database and an Elasticsearch server, wherein,
the MongoDB database is used for storing data required by the Elasticissearch server;
the synchronization node is used for acquiring a preset synchronization list and determining a set in a MongoDB database contained in the synchronization list; the method comprises the following steps that data connection is established between a plurality of synchronous nodes and a MongoDB database and an Elasticissearch server, and each synchronous node corresponds to a different synchronous list; the synchronization node monitors data change operation occurring in the set, and updates changed data to the Elasticissearch server after detecting that the data change operation occurs;
the elastic search server is used for receiving the data sent by the synchronization node;
the synchronization node comprises a stream processing module, a hash assignment module, a local fragmentation module 413, wherein,
the stream processing module is used for monitoring data change operation and sending the changed data to the hash distribution module when the data change operation is determined to occur;
the hash distribution module is used for calculating the processing number of the data processed by each local fragmentation module according to the number of the received data and the fragmentation number of the local fragmentation module, and distributing the data to the local fragmentation modules according to the processing number;
the local fragmentation module is used for determining field information of the received data, determining a mapping relation between the field information and the field information of the Elasticissearch server, finally calling a data updating interface of the Elasticissearch server, and updating the data to the Elasticissearch server according to the mapping relation.
9. A storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the server data synchronization method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110620386.6A CN113364864B (en) | 2021-06-03 | 2021-06-03 | Server data synchronization method, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110620386.6A CN113364864B (en) | 2021-06-03 | 2021-06-03 | Server data synchronization method, system and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113364864A CN113364864A (en) | 2021-09-07 |
| CN113364864B true CN113364864B (en) | 2022-09-30 |
Family
ID=77531828
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110620386.6A Active CN113364864B (en) | 2021-06-03 | 2021-06-03 | Server data synchronization method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113364864B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111767282A (en) * | 2020-06-12 | 2020-10-13 | 咪咕文化科技有限公司 | MongoDB-based storage system, data insertion method and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107544999B (en) * | 2016-06-28 | 2022-10-21 | 百度在线网络技术（北京）有限公司 | Synchronization device and synchronization method for retrieval system, and retrieval system and method |
| CN107783975B (en) * | 2016-08-24 | 2021-02-26 | 北京京东尚科信息技术有限公司 | Method and device for synchronous processing of distributed databases |
| CN109840251B (en) * | 2018-12-29 | 2023-11-03 | 北京奥鹏远程教育中心有限公司 | Big data aggregation query method |
| CN109857558A (en) * | 2019-01-18 | 2019-06-07 | 苏宁易购集团股份有限公司 | A kind of data flow processing method and system |
-
2021
- 2021-06-03 CN CN202110620386.6A patent/CN113364864B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111767282A (en) * | 2020-06-12 | 2020-10-13 | 咪咕文化科技有限公司 | MongoDB-based storage system, data insertion method and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113364864A (en) | 2021-09-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11379461B2 (en) | Multi-master architectures for distributed databases | |
| US6816860B2 (en) | Database load distribution processing method and recording medium storing a database load distribution processing program | |
| CN108121782B (en) | Distribution method of query request, database middleware system and electronic equipment | |
| CN109643310B (en) | System and method for redistribution of data in a database | |
| CN109173270B (en) | Game service system and implementation method | |
| CN109815248B (en) | Zookeeper-based distributed architecture data consistency method | |
| CN110708196B (en) | Data processing method and device | |
| CN103561055B (en) | Web application automatic elastic extended method under conversation-based cloud computing environment | |
| CN103581313B (en) | Connection establishment method for processing equipment and cluster server and processing equipment | |
| CN107368369B (en) | Distributed container management method and system | |
| CN101751415A (en) | Metadata service system metadata synchronized method and writing server updating method | |
| CN109361777B (en) | Synchronization method, synchronization system and related device for distributed cluster node states | |
| CN112231108A (en) | Task processing method and device, computer readable storage medium and server | |
| CN108875035A (en) | The date storage method and relevant device of distributed file system | |
| CN109144787A (en) | A kind of data reconstruction method, device, equipment and readable storage medium storing program for executing | |
| CN102026228A (en) | Statistical method and equipment for communication network performance data | |
| CN111694518A (en) | Method, device and equipment for automatically migrating data after cluster expansion or contraction | |
| CN113364864B (en) | Server data synchronization method, system and storage medium | |
| CN106815318B (en) | Clustering method and system for time sequence database | |
| CN111158956A (en) | Data backup method and related device for cluster system | |
| CN111858656A (en) | Static data query method and device based on distributed architecture | |
| CN111901405A (en) | Multi-node monitoring method and device, electronic equipment and storage medium | |
| CN111552701A (en) | Method for determining data consistency in distributed cluster and distributed data system | |
| CN111897839A (en) | Data processing method and system | |
| CN116401317B (en) | Cache data synchronization method and device, electronic equipment and 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 |