CN107016075A - Company-data synchronous method and device - Google Patents
Company-data synchronous method and device Download PDFInfo
- Publication number
- CN107016075A CN107016075A CN201710188682.7A CN201710188682A CN107016075A CN 107016075 A CN107016075 A CN 107016075A CN 201710188682 A CN201710188682 A CN 201710188682A CN 107016075 A CN107016075 A CN 107016075A
- Authority
- CN
- China
- Prior art keywords
- data
- sequence number
- destination node
- log files
- transaction sequence
- 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.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
Abstract
Present invention is disclosed a kind of company-data synchronous method and device.Methods described includes：Obtain the Transaction Sequence number of destination node；The Data Position of the Transaction Sequence number association is obtained in the data log files of the target cluster；According to the Data Position in the data log files, the data in the data log files since the Data Position are imported into the destination node；The importing of the data is responded, the destination node is added into the target cluster.Thus, by the present invention, destination node is when carrying out cluster synchronization, the data that data full dose is synchronous, only needs synchronous destination node to fall behind need not be carried out, company-data increment synchronization is realized, so as to greatly reduce synchrodata amount, the time needed for data syn-chronization is effectively reduced.
Description
Technical field
The present invention relates to database field, more particularly to a kind of company-data synchronous method and device.
Background technology
MySQL is a Relational DBMS, and Galera Cluster (cluster) are a set of based on synchronous multiple
The how main MySQL Cluster Solutions of system.Node in the cluster realizes the data in all nodes by synchronous real-time update
Uniformity.When there is node to have two kinds of methods of synchronization at present when adding Galera Cluster, one kind is IST
(Incremental State Transfer, increment synchronization mode), is characterized in light weight and quick, another is SST, i.e.,
State Snapshot Transfer, SST are the full dose methods of synchronization, i.e., synchronous total data, are characterized in that data volume is eased up greatly
Slowly.
When node adds Galera Cluster, seqno (the Sequence Number, affairs of the node can be first judged
Sequence number) it whether there is in Galera Cluster GCache files, if in Galera Cluster GCache files
It is middle then to open IST in the presence of the seqno,, will if there is no SST is then opened by the data syn-chronization in cluster to this node
All data full doses are synchronized to this node in Galera Cluster.
It is not many when the node newly added is differed with Galera Cluster data, but (cluster cache is literary by GCache
Part) in file again without corresponding seqno when, then it is synchronous to carry out full dose by SST modes, and not only lock in time can be compared with
It is long, and obstruction can be produced, eventually influence Galera Cluster normally to run.
Therefore, if adding the destination node in Galera Cluster, there is no the destination node in GCache files
Transaction Sequence number seqno when, even if only having fallen behind a part of data in the destination node, can only also carry out full dose same
Step, because the synchronous data volume of full dose is larger, causing the destination node, synchronously required time can be relatively more in company-data.
The content of the invention
The problem of in order to solve to take more when company-data present in correlation technique is synchronous, the invention provides one kind
Company-data synchronous method and device.
A kind of company-data synchronous method, methods described includes：
Obtain the Transaction Sequence number of destination node；
The Data Position of the Transaction Sequence number association is obtained in the data log files of the target cluster；
According to the Data Position in the data log files, it will be opened in the data log files from the Data Position
The data of beginning import the destination node；
The importing of the data is responded, the destination node is added into the target cluster.
A kind of company-data sychronisation, described device includes：
Transaction Sequence number acquisition module, the Transaction Sequence number for obtaining destination node；
Data Position acquisition module, for obtaining the Transaction Sequence number in the data log files of the target cluster
The Data Position of association；
Data import modul, for the Data Position in the data log files, by the data log files
In data since the Data Position import the destination node；
Cluster adds module, and the destination node is added the target cluster by the importing for responding the data.
The technical scheme that embodiments of the invention are provided can include the following benefits：
Transaction Sequence number of the invention by obtaining destination node, obtains the thing in the data log files of target cluster
Be engaged in the Data Position of sequence number association, according to the Data Position in the data log files, by the data log files from this
Data that Data Position starts import destination node, and respond after the completion of the importing of the data imports data to, by the target
Node adds the target cluster.The Transaction Sequence number is obtained in the data log files of target cluster by Transaction Sequence number to close
The Data Position of connection, and according to the Data Position, import data to the destination node, destination node is finally added to object set
Group, realizes the increment synchronization of data, so as to effectively reduce the time needed for data syn-chronization.
It should be appreciated that the general description of the above and detailed description hereinafter are only exemplary, this can not be limited
It is open.
Brief description of the drawings
Accompanying drawing herein is merged in specification and constitutes the part of this specification, shows the implementation for meeting the present invention
Example, and in specification together for explaining principle of the invention.
Fig. 1 is the schematic diagram according to implementation environment involved in the present invention；
Fig. 2 is a kind of flow chart of company-data synchronous method according to an exemplary embodiment；
Fig. 3 is the flow chart that step S210 details is described for correspondingly being implemented to exemplify according to Fig. 2；
Fig. 4 is the flow chart that step S230 details is described for correspondingly being implemented to exemplify according to Fig. 2；
Fig. 5 is the flow chart that step S250 details is described for correspondingly being implemented to exemplify according to Fig. 2；
Fig. 6 is a kind of block diagram of company-data sychronisation according to an exemplary embodiment；
Fig. 7 is the block diagram that the details of Transaction Sequence number acquisition module is described for correspondingly being implemented to exemplify according to Fig. 6；
Fig. 8 is the block diagram that the details of data position acquisition module is described for correspondingly being implemented to exemplify according to Fig. 6；
Fig. 9 is the block diagram that the details of data import modul is described for correspondingly being implemented to exemplify according to Fig. 6.
Embodiment
Here explanation will be performed to exemplary embodiment in detail, its example is illustrated in the accompanying drawings.Following description is related to
During accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represent same or analogous key element.Following exemplary embodiment
Described in embodiment do not represent and the consistent all embodiments of the present invention.On the contrary, they be only with it is such as appended
The example of the consistent apparatus and method of some aspects be described in detail in claims, the present invention.
Fig. 1 is the schematic diagram according to implementation environment involved in the present invention.The implementation environment includes：Cluster 110, node
130 and cluster in more than one node, node 120, node 121, node 122 in such as Fig. 1.
Wherein, node 120, node 121, node 122 are the nodes in cluster, are single numbers before cluster is added
According to storehouse node, cluster can be set up or added to one or more single database nodes, node 130 is database node,
Node 130 can also be started by way of cluster.
Implementation environment as shown in Figure 1 can have a cluster 110, also in the presence of some company-data
Node 130 with the data of cluster 110 by node 130, it is necessary to carry out increment synchronization.
Interrelational form between cluster 110 and node 130, including wired or wireless network associate mode, and the two
Between the data correlation mode come and gone, specific interrelational form do not limited by the present embodiment.
The interrelational form between node in cluster 110 and cluster 110, including wired or wireless network associate mode,
And the data correlation mode come and gone therebetween, specific interrelational form do not limited by the present embodiment.
The interrelational form between node in node 130 and cluster 110, including wired or wireless network associate mode,
And the data correlation mode come and gone therebetween, specific interrelational form do not limited by the present embodiment.
Interrelational form between node 120, node 121, node 122, including wired or wireless network associate mode, with
And the data correlation mode come and gone therebetween, specific interrelational form do not limited by the present embodiment.
Fig. 2 is a kind of flow chart of company-data synchronous method according to an exemplary embodiment.As shown in Fig. 2
The company-data synchronous method may comprise steps of.
In step S210, the Transaction Sequence number of destination node is obtained.
Wherein, destination node, refers to database node to be synchronized, and does not add in cluster now, i.e. the data
Data in the node of storehouse lag behind the node 130 in the data in cluster interior joint, such as Fig. 1.Transaction Sequence number refers to database
Node has performed numbering during last affairs, database node during affairs are performed, according to affairs perform it is complete
Transaction Sequence number is adjusted into situation.The Transaction Sequence number can automatically be counted according to the implementation status of affairs, for example, often holding
An affairs are gone, Transaction Sequence number adds 1 automatically.
Because each node can have the Transaction Sequence number of oneself, and each sequence number is in data log files, all
It is able to can be recorded by distributed sequence number, also, content corresponding with this distributed sequence number includes the transaction sequence
Number corresponding affairs perform Data Position associated when completing.The Data Position is exactly the starting position for carrying out data importing.
The Data Position is only got, just can know that data wherefrom start importing.
For example, because the reason such as capacity requirement change or clustering fault, after node 130 is offline from cluster 110, now,
The Transaction Sequence number got from the node 130 is exactly a fixed numerical value, such as 50096.Any one in cluster 110
In data log files in individual node, the mode for sequence number in a distributed manner records the Transaction Sequence number of node 130, i.e., in number
According in journal file, can be distributed be Serial No. 50096 content.The distributed sequence number is found, phase is also just have found
The Data Position of association.Therefore, Data Position when data start importing has just been obtained.
The mode of the Transaction Sequence number of destination node is obtained, both can send Transaction Sequence number to destination node obtains life
Order, can also be obtained by cluster recovery order.Generally, it can be obtained sending Transaction Sequence number to destination node
After order, when not receiving the Transaction Sequence number of return or the Transaction Sequence number of return for error identification, then it is extensive by cluster
Report on completion of a task order to obtain, the cluster recovery order can be mysqld_safe--wsrep-recover.
In step S230, the Data Position of Transaction Sequence number association is obtained in the data log files of target cluster.
Wherein, target cluster, refers to the cluster being in running status, now, cluster is ensured that in cluster interior joint
Data in data consistency, therefore the cluster in any one node are consistent, such as Fig. 1 clusters 110.In this situation
Under, node 120, node 121, the data of node 122 are consistent.
Data log files, refer to the associated documents generated according to database processing affairs, also commonly referred to as binary system
Journal file, such as binlog files.In the content of data log files, distributed sequence number, such as xid=there are
50096, the Transaction Sequence number that each distributed sequence number is corresponding when being an affairs completion, and also each is distributed
Sequence number also to that should have Data Position associated during an affairs completion, can determine that the position that next affairs start accordingly
Put.
The storage of data typically has starting position and end position, in this programme, and Data Position refers to next affairs
Starting position, i.e. Current transaction end position.
In step s 250, the Data Position in data log files, by the data log files from data
The data that position starts import destination node.
According to step S230, after the Data Position for obtaining Transaction Sequence number association, to database since the Data Position
Operated accordingly.
Wherein, it is that the data in data log files are imported into destination node since the Data Position in this programme,
Data that will be in the data log files since Data Position import destination node.
That is, imported and ordered according to data, the data of data log files are imported into target section successively since Data Position
Point.For example, the Data Position for getting the association of Transaction Sequence number 50096 is 399, then since position 399, by data logging
Data in file all imported into destination node.
Further, when the data log files in a cluster interior joint are two or more, that is, there are several numbers
, can be according to the characteristics of data log files during according to journal file, such as time of generation, the file name of generation, will be all
Data log files form data log files queue in sequence.It is such as suitable according to time sequencing or according to filename
Sequence, then finds the data log files where Transaction Sequence number, further according to step S230 and S250 by data log files
Data since Data Position import destination node, after the completion of data log files processing, then by data log files
The data that queue comes all data log files behind the data log files all import destination node.
For example, there are 213 journal files, file entitled hs-bin.0001, hs-bin.0002, hs- in node 121
Bin.0003, in this order to last journal file hs-bin.0213.The Transaction Sequence number of node 130 is 50096.Root
According to this 213 data log files are formed into a data log files queues the characteristics of file name, then in this data
Transaction Sequence number 50096 is found in data log files in journal file queue, such as finally finds the Transaction Sequence number
50096 in hs-bin.0111 this data log files, determine the Transaction Sequence number in hs- further according to step S230
The Data Position associated in this data log files of bin.0111, finally according to step S250 by this number of hs-bin.0111
According to the data in journal file since delivery node 130 the Data Position of the association.After the completion of importing, then by data logging
The later data log files of hs-bin.0111 this data log files, the i.e. entitled hs- of file are come in file
Bin.0112, hs-bin.0113, hs-bin.0114 arrive the hs-bin.0213 whole delivery nodes of data successively in this order
In 130.
By it is possible thereby to determine Transaction Sequence number in hs-bin.0111 this data log files.Certainly can be with
Determine that the Transaction Sequence number 50096 has hs-bin.0111 this data logging texts using other methods or algorithm etc.
In part.
In step S270, destination node is added the target cluster by the importing of response data.
The step S250 data imported are responded, completed until data are imported.As illustrated, node 130 is in data
After the completion of importing, the synchronization of data is now completed, you can add the node 130 in cluster 110.
Using process as described above, obtain the Transaction Sequence number of destination node, by the Transaction Sequence number get with
The Data Position of Transaction Sequence number association, imports data to the destination node since the Data Position, and response data is imported,
The destination node is added in target cluster after data importing terminates.I.e. when the cluster cache file (example in clustered node
Such as, GCache files) in the Transaction Sequence number is not present in the case of, it is synchronous without carrying out data full dose, only need increment synchronization
.Thus, just realize by the data Fast synchronization in destination node and target cluster, so as to effectively reduce data syn-chronization
The required time.
Fig. 3 is the flow chart that step S210 details is described for correspondingly being implemented to exemplify according to Fig. 2.The step
S210, as shown in figure 3, may comprise steps of.
In step S211, send Transaction Sequence number to destination node and obtain order.
Wherein, it can obtain in cluster state file (such as grastate.dat files) that Transaction Sequence number, which obtains order,
Transaction Sequence number order.
In step S213, the Transaction Sequence number that destination node response transactions sequence number obtains order and returned is received.
Destination node receives Transaction Sequence number and obtained after order, can perform the order and be responded, and will perform the order
The Transaction Sequence number of acquisition returns to the destination node and sends the side that Transaction Sequence number obtains order.
Fig. 4 is the flow chart that step S230 details is described for correspondingly being implemented to exemplify according to Fig. 2.The step
S230, as shown in figure 4, may comprise steps of.
In step S231, the distributed sequence number in the data log files of target cluster is obtained.
Wherein, data log files include multinomial content, there is a data log files title, starting position, transaction types,
Clustered node is numbered, end position, remark information etc..
Database, which is often performed, will produce a distributed sequence number in an affairs, data log files.Therefore, each
In data log files, it is understood that there may be multiple distributed sequence numbers.Looked into by sending distributed sequence number to data log files
Ask order, you can obtain the distributed sequence number in the data log files of the target cluster.
When affairs, which are performed, to be completed, corresponding Transaction Sequence number can be generated, and according to the node for performing the affairs, generation
Corresponding data log files.The content of the data log files can include the node serial number of the execution affairs, distributed
Sequence number, and distributed sequence number is identical with the Transaction Sequence number.
In step S233, for each distributed sequence number, distributed sequence number and the Transaction Sequence number are carried out
Contrast, if unanimously, the corresponding Data Position of distributed sequence number to be defined as to the Data Position of Transaction Sequence number association.
The step S231 distributed sequence numbers obtained are contrasted with Transaction Sequence number one by one, if there is it is consistent when,
The corresponding Data Position of distributed sequence number can be defined as to the Data Position of Transaction Sequence number association, that is, represent and have found this
The Data Position of Transaction Sequence number association.
Further, when the data log files in a cluster interior joint are two or more, that is, there are multiple data day
During will file.The time of data log files generation each first can be different, i.e., the data log files time first generated is early
In the data log files of rear generation, secondly, the name of each data log files generation also can be different, typically all by numeral
The order name of numbering, furthermore the size of each data log files is also possible to meeting difference.
, can be according to these data log files in itself when there are multiple data log files in i.e. one cluster interior joint
The characteristics of, filename or by way of the time, data log files queue is formed, it is literary further according to the data logging in team
Distributed sequence number in part determines the data log files where Transaction Sequence number, then leads in the data log files
Cross the position that distributed sequence number finds Transaction Sequence number association.
Thus, can be according to as above feature, by all data log files in the case of multiple data log files
Data log files queue is formed in sequence., should by traversal such as according to time sequencing or according to order of file names
The data log files of data log files queue obtain first distributed sequence number of each data log files, Ran Hougen
The data log files where Transaction Sequence number are obtained according to these distributed sequence numbers.After the journal file is found, then pass through
Step S231 eventually finds the Data Position that the Transaction Sequence number is associated with S233.
For example, there are 213 journal files, file entitled hs-bin.0001, hs-bin.0002, hs- in node 121
Bin.0003, in this order to last journal file hs-bin.0213.The Transaction Sequence number of node 130 is 50096, hs-
The distributed sequence number 1 of first of bin.0001, hs-bin.0002 first distributed sequence number 315, hs-bin.0003
First distributed sequence number 768, the then distributed sequence number 49999, hs-bin.0112 of the first of hs-bin.0111
First distributed sequence number 50398, hs-bin.0213 first distributed sequence number 110398.Because 49999<
50096<50398, it is possible thereby to determine Transaction Sequence number in hs-bin.0111 this data log files.Certainly can be with
Determine that the Transaction Sequence number 50096 has hs-bin.0111 this data logging texts using other methods or algorithm etc.
In part.Then the distributed sequence number in hs-bin.0111 this data log files is obtained by step S231, according to S233
These distributed sequence numbers are contrasted with Transaction Sequence number one by one, and eventually find the data bit of Transaction Sequence number association
Put.
Fig. 5 is the flow chart that step S250 details is described for correspondingly being implemented to exemplify according to Fig. 2.The step
S250, as shown in figure 5, may comprise steps of.
In step S251, it is new cluster that destination node, which is started,.
Wherein, for the new cluster compares target cluster, there are some differences, the title of such as cluster, configuration etc. has area
Not.Destination node is started after being new cluster, for the data syn-chronization in target cluster and new cluster, compatibility and stably
Property is higher.
Further, the external Service Privileges of database in destination node can also be closed.Saved to reduce in cluster
In point, new real time data is produced, so as to influence to data syn-chronization, the external Service Privileges of destination node can be closed, so
Under off-line state, data increment synchronization is carried out, isolation processing has quite such as been done, has reduced the interference of data, so as to more carry
Compatibility and stability are risen.
In step S253, by the data in data log files since Data Position, the target imported in new cluster
Node.
I.e. by the data in the data log files in target cluster interior joint, the destination node importeding into new cluster
In, wherein, when data are imported, using Data Position as original position.
Wherein, new cluster refer to compare cluster 110 for there is the different cluster of the information such as title, i.e. node 130 is used
Cluster name or configuration information beyond cluster 110 are started by trunking mode.The external Service Privileges of database are externally to hold
The authority of row data transactions, closes the processing that this authority illustrates to stop db transaction, that is, closes after external Service Privileges
The data that will not be produced in new data transactions, database no longer change.Data are advantageously reduced by this two operations
Occur mistake when synchronous, consequently reduce company-data synchronous required time.
Following is apparatus of the present invention embodiment, can be used for performing above-mentioned company-data synchronous method embodiment of the invention.
For the details not disclosed in apparatus of the present invention embodiment, company-data synchronous method embodiment of the present invention refer to.
Fig. 6 is a kind of block diagram of company-data sychronisation according to an exemplary embodiment.The company-data is same
Step device can be used in the implementation environment shown in Fig. 1, perform all or part of step of the company-data synchronous method shown in Fig. 2
Suddenly.As shown in fig. 6, the company-data sychronisation 300 includes but is not limited to：Transaction Sequence number acquisition module 310, Data Position
Acquisition module 330, data import modul 350 and cluster add module 370.
Transaction Sequence number acquisition module 310, the Transaction Sequence number for obtaining destination node.
Data Position acquisition module 330, for obtaining Transaction Sequence number association in the data log files of target cluster
Data Position.
Data import modul 350, for the Data Position in data log files, by data log files from number
The data started according to position import destination node.
Cluster adds module 370, and for the importing of response data, destination node is added into target cluster.
Fig. 7 is the block diagram that the details of Transaction Sequence number acquisition module is described for correspondingly being implemented to exemplify according to Fig. 6.
As shown in fig. 7, the Transaction Sequence number acquisition module 310 includes but is not limited to：Transmitting element 311 and receiving unit 313.
Transmitting element 311, order is obtained for sending Transaction Sequence number to destination node.
Receiving unit 313, for receiving the Transaction Sequence number that destination node response transactions sequence number obtains order and returned.
Fig. 8 is the block diagram that the details of data position acquisition module is described for correspondingly being implemented to exemplify according to Fig. 6.Such as
Shown in Fig. 8, the Data Position acquisition module 330 includes but is not limited to：Acquiring unit 331 and comparison unit 333.
Acquiring unit 331, the distributed sequence number in data log files for obtaining target cluster.
Comparison unit 333, for for each distributed sequence number, by distributed sequence number and Transaction Sequence number progress pair
Than if unanimously, the corresponding Data Position of distributed sequence number to be defined as to the Data Position of Transaction Sequence number association.
Fig. 9 is the block diagram that the details of data import modul is described for correspondingly being implemented to exemplify according to Fig. 6.Such as Fig. 9
Shown, the data import modul 350 includes but is not limited to：Start unit 351 and import unit 353.
Start unit 351, is new cluster for destination node to be started.
Import unit 353, for by the data in data log files since Data Position, the mesh imported in new cluster
Mark node.
It should be appreciated that the invention is not limited in the precision architecture for being described above and being shown in the drawings, and
And various modifications and changes can be being performed without departing from the scope.The scope of the present invention is only limited by appended claim.
Claims (8)
1. a kind of company-data synchronous method, it is characterised in that methods described includes：
Obtain the Transaction Sequence number of destination node；
The Data Position of the Transaction Sequence number association is extracted in the data log files of the target cluster；
According to the Data Position in the data log files, by the data log files since the Data Position
Data import the destination node；
The importing of the data is responded, the destination node is added into the target cluster.
2. according to the method described in claim 1, it is characterised in that the Transaction Sequence number for obtaining destination node, including：
Transaction Sequence number, which is sent, to the destination node obtains order；
Receive the destination node and respond the Transaction Sequence number that the Transaction Sequence number obtains order and returned.
3. according to the method described in claim 1, it is characterised in that described to be obtained in the data log files of the target cluster
The Data Position of the Transaction Sequence number association is taken, including：
Obtain the distributed sequence number in the data log files of the target cluster；
For each distributed sequence number, the distributed sequence number and the Transaction Sequence number are contrasted, if unanimously,
The corresponding Data Position of the distributed sequence number is then defined as to the Data Position of the Transaction Sequence number association.
4. according to the method described in claim 1, it is characterised in that the data bit in the data log files
Put, the data in the data log files since the Data Position are imported into the destination node, including：
It is new cluster that the destination node, which is started,；
By the data in the data log files since the Data Position, the destination node imported in the new cluster.
5. a kind of company-data sychronisation, it is characterised in that described device includes：
Transaction Sequence number acquisition module, the Transaction Sequence number for obtaining destination node；
Data Position acquisition module, for obtaining the Transaction Sequence number association in the data log files of the target cluster
Data Position；
Data import modul, for the Data Position in the data log files, by the data log files from
The data that the Data Position starts import the destination node；
Cluster adds module, and the destination node is added the target cluster by the importing for responding the data.
6. device according to claim 5, it is characterised in that the Transaction Sequence number acquisition module, including：
Transmitting element, order is obtained for sending Transaction Sequence number to the destination node；
Receiving unit, the transaction sequence that the Transaction Sequence number obtains order and returned is responded for receiving the destination node
Number.
7. device according to claim 5, it is characterised in that the Data Position acquisition module, including：
Acquiring unit, the distributed sequence number in data log files for obtaining the target cluster；
Comparison unit, for for each distributed sequence number, the distributed sequence number and the Transaction Sequence number to be carried out
Contrast, if unanimously, the corresponding Data Position of the distributed sequence number to be defined as to the number of the Transaction Sequence number association
According to position.
8. device according to claim 5, it is characterised in that the data import modul, including：
Start unit, is new cluster for the destination node to be started；
Import unit, for by the data in the data log files since the Data Position, importing the new cluster
In destination node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710188682.7A CN107016075A (en) | 2017-03-27 | 2017-03-27 | Company-data synchronous method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710188682.7A CN107016075A (en) | 2017-03-27 | 2017-03-27 | Company-data synchronous method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107016075A true CN107016075A (en) | 2017-08-04 |
Family
ID=59445085
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710188682.7A Pending CN107016075A (en) | 2017-03-27 | 2017-03-27 | Company-data synchronous method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107016075A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908652A (en) * | 2017-10-12 | 2018-04-13 | 北京人大金仓信息技术股份有限公司 | A kind of Sequence implementation methods for distributed data base system |
| CN110287164A (en) * | 2019-06-28 | 2019-09-27 | 联想(北京)有限公司 | A kind of data reconstruction method, device and computer equipment |
| CN111209251A (en) * | 2019-12-27 | 2020-05-29 | 山大地纬软件股份有限公司 | Data increment synchronization system and method for data archiving system |
| CN112579550A (en) * | 2020-12-21 | 2021-03-30 | 国电南瑞科技股份有限公司 | Metadata information synchronization method and system of distributed file system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101751394A (en) * | 2008-12-16 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for synchronizing data |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN104239493A (en) * | 2014-09-09 | 2014-12-24 | 北京京东尚科信息技术有限公司 | Cross-cluster data migration method and system |
| US9020888B1 (en) * | 2012-04-04 | 2015-04-28 | Nectar Services Corp. | Data replicating systems and data replication methods |
| CN105574187A (en) * | 2015-12-23 | 2016-05-11 | 武汉达梦数据库有限公司 | Duplication transaction consistency guaranteeing method and system for heterogeneous databases |
| US20160371319A1 (en) * | 2015-06-19 | 2016-12-22 | Sap Se | Synchronization on reactivation of asynchronous table replication |
-
2017
- 2017-03-27 CN CN201710188682.7A patent/CN107016075A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101751394A (en) * | 2008-12-16 | 2010-06-23 | 青岛海信传媒网络技术有限公司 | Method and system for synchronizing data |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| US9020888B1 (en) * | 2012-04-04 | 2015-04-28 | Nectar Services Corp. | Data replicating systems and data replication methods |
| CN104239493A (en) * | 2014-09-09 | 2014-12-24 | 北京京东尚科信息技术有限公司 | Cross-cluster data migration method and system |
| US20160371319A1 (en) * | 2015-06-19 | 2016-12-22 | Sap Se | Synchronization on reactivation of asynchronous table replication |
| CN105574187A (en) * | 2015-12-23 | 2016-05-11 | 武汉达梦数据库有限公司 | Duplication transaction consistency guaranteeing method and system for heterogeneous databases |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908652A (en) * | 2017-10-12 | 2018-04-13 | 北京人大金仓信息技术股份有限公司 | A kind of Sequence implementation methods for distributed data base system |
| CN110287164A (en) * | 2019-06-28 | 2019-09-27 | 联想(北京)有限公司 | A kind of data reconstruction method, device and computer equipment |
| CN110287164B (en) * | 2019-06-28 | 2021-07-16 | 联想(北京)有限公司 | Data recovery method and device and computer equipment |
| CN111209251A (en) * | 2019-12-27 | 2020-05-29 | 山大地纬软件股份有限公司 | Data increment synchronization system and method for data archiving system |
| CN112579550A (en) * | 2020-12-21 | 2021-03-30 | 国电南瑞科技股份有限公司 | Metadata information synchronization method and system of distributed file system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106534273B (en) | Block chain metadata storage system and storage method and retrieval method thereof | |
| CN111209346B (en) | Block chain data archiving method and device and computer readable storage medium | |
| EP4155966A1 (en) | Blockchain data indexing method, and blockchain data storage method | |
| US7778962B2 (en) | Client store synchronization through intermediary store change packets | |
| US10417103B2 (en) | Fault-tolerant methods, systems and architectures for data storage, retrieval and distribution | |
| CN104537076B (en) | A kind of file read/write method and device | |
| CN107924408B (en) | System and method for searching heterogeneous index of metadata and tags in file system | |
| CN107016075A (en) | Company-data synchronous method and device | |
| US20070143286A1 (en) | File management method in file system and metadata server therefor | |
| US20170031948A1 (en) | File synchronization method, server, and terminal | |
| CN106462639A (en) | Processing mutations for remote database | |
| CN106815326A (en) | A kind of system and method for detecting dereliction key data table uniformity | |
| CN106503158A (en) | Method of data synchronization and device | |
| CN110245134B (en) | Increment synchronization method applied to search service | |
| CN110737719A (en) | Data synchronization method, device, equipment and computer readable storage medium | |
| CN110598413A (en) | Method, system and equipment for maintaining rules of anti-attack platform | |
| CN109189759A (en) | Method for reading data, data query method, device and equipment in KV storage system | |
| CN112698622B (en) | Automatic control method, device and machine readable storage medium | |
| CN112202909B (en) | Online upgrading method and system for computer storage system | |
| CN113672692A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN112231324B (en) | System and method for realizing incremental data comparison | |
| CN110442645A (en) | Data index method and device | |
| CN111147226A (en) | Data storage method, device and storage medium | |
| US8705537B1 (en) | Eventually-consistent data stream consolidation | |
| CN112000671A (en) | Block chain-based database table processing method, device and system |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170804 |
|
| RJ01 | Rejection of invention patent application after publication |