CN105208060A - Service data synchronization method, service data synchronization device and service data synchronization system - Google Patents
Service data synchronization method, service data synchronization device and service data synchronization system Download PDFInfo
- Publication number
- CN105208060A CN105208060A CN201410277682.0A CN201410277682A CN105208060A CN 105208060 A CN105208060 A CN 105208060A CN 201410277682 A CN201410277682 A CN 201410277682A CN 105208060 A CN105208060 A CN 105208060A
- Authority
- CN
- China
- Prior art keywords
- server
- change
- business
- task identification
- queue
- 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.)
- Granted
Links
Abstract
The invention discloses a service data synchronization method, a service data synchronization device and a service data synchronization system. The method comprises the steps as follows: calling a service change queue of a second server when service data after change on a first server needs to be synchronized to the second server, wherein the service change queue contains at least one task identifier, and each task identifier corresponds to one service change on the first server; and synchronizing the service data after service change corresponding to each task identifier to the second server according to the establishment order of the task identifiers in the service change queue. According to the embodiment of the invention, service change maintenance operation can be concentrated in a data center where a service data changer is located, and therefore, service change maintenance operation by other data centers is alleviated; and a task processor synchronizes service data after change in a unified manner, which can alleviate the processing burden of the data centers.
Description
Technical field
The application relates to network communication technology field, particularly relates to synchronizing traffic data method, Apparatus and system.
Background technology
Along with the arriving of large data age, Internet enterprises is when carrying out miscellaneous service, magnanimity business datum can be produced, in order to carry out unified management to business datum, usual needs set up data center in various places, safeguard identical business datum in these data centers, so that client device accesses local data center by local area network, thus business datum can be obtained fast.Wherein, when the business datum of certain data center occurs to change, other data centers are needed synchronously to change business datum, to reach the consistency of business datum.
In prior art, in order to ensure the order that business datum changes, need the colophon that each data center maintenance business datum changes, when receiving the change request of business datum, if this request ask the version of business datum changed to be preserved higher than current data center version time, execution business datum changes, otherwise refusal changes business datum.But, because existing each data center needs the change maintenance release record for business datum, therefore make the attended operation of each data center become loaded down with trivial details, and the process need changing business datum carry out version contrast, because this increasing the processing load of each data center.
Summary of the invention
The application provides synchronizing traffic data method, Apparatus and system, carries out business datum change, cause attended operation loaded down with trivial details to solve each data center existing by maintenance release record, and the problem that processing load is heavier.
According to the first aspect of the embodiment of the present application, provide a kind of synchronizing traffic data method, described method comprises:
When will by the change in first server after synchronizing traffic data to second server time, call the business change queue of described second server, at least one task identification is comprised, a business change in the corresponding described first server of each task identification in described business change queue;
According to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
According to the second aspect of the embodiment of the present application, provide a kind of synchronizing traffic data device, described device comprises:
Call unit, for when will by the change in first server after synchronizing traffic data to second server time, call the business change queue of described second server, at least one task identification is comprised, a business change in the corresponding described first server of each task identification in described business change queue;
Lock unit, for according to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
According to the third aspect of the embodiment of the present application, provide a kind of business data synchronization system, described system comprises: task processor, first server and at least one second server, wherein,
Described first server, for changing queue for each described second server maintenance service, comprises at least one task identification in described business change queue, a business change in the corresponding described first server of each task identification;
Described task processor, for when will by the change in first server after synchronizing traffic data to described second server time, call the business change queue of described second server; According to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
When the embodiment of the present application carries out synchronizing traffic data, by the second server maintenance service change queue that the first server that business datum change occurs is business datum after needs synchronously change, so that task processor is after calling business change queue, according to task identification in business change queue from the foundation order after arriving first, by synchronizing traffic data after the change corresponding with each task identification to second server.Application the embodiment of the present application, the attended operation of business change can be concentrated on the data center at place, the business datum side of change, thus alleviate the attended operation of other data centers to business change, and carried out synchronously, the processing load of each data center can being alleviated to business datum after change by task processor unification.
Should be understood that, it is only exemplary and explanatory that above general description and details hereinafter describe, and can not limit the application.
Accompanying drawing explanation
Accompanying drawing to be herein merged in specification and to form the part of this specification, shows the embodiment meeting the application, and is used from specification one principle explaining the application.
Fig. 1 is the embodiment block diagram of the application's business data synchronization system;
Fig. 2 is an embodiment flow chart of the application's synchronizing traffic data method;
Fig. 3 is the data center systems configuration diagram adopting the embodiment of the present application to realize synchronizing traffic data;
Fig. 4 is another embodiment flow chart of the application's synchronizing traffic data method;
Fig. 5 is an embodiment block diagram of the application's synchronizing traffic data device;
Fig. 6 is another embodiment block diagram of the application's synchronizing traffic data device.
Embodiment
Only for describing the object of specific embodiment at term used in this application, and not intended to be limiting the application." one ", " described " and " being somebody's turn to do " of the singulative used in the application and appended claims is also intended to comprise most form, unless context clearly represents other implications.It is also understood that term "and/or" used herein refer to and comprise one or more project of listing be associated any or all may combine.
Term first, second, third, etc. may be adopted although should be appreciated that to describe various information in the application, these information should not be limited to these terms.These terms are only used for the information of same type to be distinguished from each other out.Such as, when not departing from the application's scope, the first information also can be called as the second information, and similarly, the second information also can be called as the first information.Depend on linguistic context, word as used in this " if " can be construed as into " ... time " or " when ... time " or " in response to determining ".
Along with the arriving of large data age, Internet enterprises, when carrying out miscellaneous service, by setting up the data center of globalization, can carry out unified management to the magnanimity business datum produced.According to the distribution of globalization business, usually need to set up data center in zones of different, each data center is by the identical business datum of set server maintenance.In order to reach the consistency of various places business datum, when the business datum of certain data center occurs to change, other data centers are needed synchronously to change business datum.Different from the colophon needing each data center to change in local maintenance business datum in prior art, the attended operation of business change is concentrated on the data center at place, the business datum side of change by the embodiment of the present application, and by task processor unification, business datum after change is carried out synchronously, thus the processing load of each data center can be alleviated.
See Fig. 1, the embodiment block diagram for the application's business data synchronization system:
This system comprises: task processor 110, first server 120 and at least one second server 130, and wherein, each server can correspond to the data center in certain region.
Wherein, described first server 120, for changing queue for each described second server maintenance service, comprises at least one task identification in described business change queue, a business change in the corresponding described first server of each task identification;
Described task processor 110, for when will by the change in first server after synchronizing traffic data to described second server time, call the business change queue of described second server; According to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
In the above-described embodiments, described first server 120, can also be used for for described second server sets up business change queue, when there is business change in described first server, for daily record is changed in described business change generation, described change log packet is containing the business datum rear with change of business datum before changing of described business change; For task identification is set up in described business change; Described task identification order is inserted in described business change queue; Preserve the corresponding relation of described task identification and described change daily record.
In the above-described embodiments, for the construction scale situation of data center in whole system, when construction scale is less, when namely second server quantity is less than predetermined number, task processor can be integrated in first server; When construction scale is larger, when second server quantity is not less than predetermined number, task processor can be arranged separately independent of first server.
As seen from the above-described embodiment, the attended operation of business change can be concentrated on the data center at place, the business datum side of change by business data synchronization system, thus alleviate the attended operation of other data centers to business change, and carried out synchronously, the processing load of each data center can being alleviated to business datum after change by task processor unification.
Below in conjunction with the embodiment of aforementioned the application's business data synchronization system, the embodiment of the application's synchronizing traffic data method and apparatus is described in detail.
See Fig. 2, be an embodiment flow chart of the application's synchronizing traffic data method, this embodiment is described from task processor side:
Step 201: when will by the change in first server after synchronizing traffic data to second server time, call the business change queue of second server, at least one task identification is comprised, a business change in the corresponding first server of each task identification in this business change queue.
In the present embodiment, suppose that business change side is first server, can be then that second server maintenance service changes queue by first server, when first server there is a business change, just can generate a task identification for this business change, and this task identification order is inserted in business change queue, namely each task identification can business datum after the change that generates of a corresponding business change, and the position of this task identification in business change queue can represent the sequencing that this business change occurs.
Step 202: according to task identification in business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to second server.
Task processor will by the change in first server after synchronizing traffic data to second server time, the business change queue that first server is safeguarded is called, because the task identification in this business change queue is that the sequencing occurred according to business change is inserted in business change queue, therefore task processor can from business change queue according to task identification from the foundation order after arriving first, obtain a task identification successively, and by with obtain task identification corresponding to business change change after synchronizing traffic data to second server, can ensure to change the synchronous of rear business datum according to business change order to second server with this, thus ensure, on second server, the out of order of synchronizing traffic data to occur.
As seen from the above-described embodiment, the attended operation of business change can be concentrated on the data center at place, the business datum side of change by business data synchronization system, thus alleviate the attended operation of other data centers to business change, and carried out synchronously, the processing load of each data center can being alleviated to business datum after change by task processor unification.
See Fig. 3, the data center systems configuration diagram for adopting the embodiment of the present application to realize synchronizing traffic data:
Data center systems framework shown in Fig. 3 comprises: divide data server A, the data server B, the data server C and data server D that are located at different regions, and carries out the task processor of synchronous process to business change data.It should be noted that, what the arbitrary data server shown in Fig. 3 represented is certain area build the data server set of data center, do not limit this data center and only comprise a data server.
In Fig. 3, tentation data server A generation business change, then data server A is data server B, data server C, data server D maintenance service change queue respectively, and by task processor by the task identification in each business change queue of isochronous schedules, according to business change on data server A from the order after arriving first, by synchronizing traffic data after the change of each business change on data server B, data server C, data server D.
See Fig. 4, be another embodiment flow chart of the application's synchronizing traffic data method, the data center systems framework in this embodiment composition graphs 3 is described:
Step 401: first server is that second server sets up business change queue.
In the present embodiment, first server is business change generation side, and second server is business change recipient, composition graphs 3, and first server is data server A, and second server is data server B, data server C, data server D.Wherein, data server A can set up business change queue respectively for data server B, data server C, data server D, on data server A, a processing threads can be opened for each business change queue, for safeguarding business change queue.
Step 402: when first server occurs in business change, changes daily record and task identification for this business change generates.
Because the business not timing in first server is changed, for business change each time, first server all can generate corresponding task identification, and record changes daily record, comprises the business datum before changing of this business change and change rear business datum in this change daily record.
Composition graphs 3, when data server A there is business change, data server A generates a task identification for this business change, as namely the numeral " 1,2 ... .n " in business change queue each in Fig. 3 represents task identification, and numeral order from small to large illustrates business change from the order of occurrence after arriving first.Such as, when data server A occurs in business change first, generate task identification 1, when there is second time business change, generate task identification 2, by that analogy, when there is n-th business change, generate task identification n.
Step 403: first server preserves task identification and the corresponding relation changing daily record.
Step 404: task identification order is inserted in business change queue by first server.
Due in data center systems except first server, also comprise multiple second server, therefore in step 401, in fact first server needs for each second server sets up business change queue, accordingly, in this step, task identification order is inserted in the business change queue of each second server by first server.Such as, task identification 2, after data server A generates task identification 2, inserts in queue B, queue C, queue D by composition graphs 3 respectively.
Step 405: when synchronously changing rear business datum, task processor calls the business change queue of second server.
In the present embodiment, task processor can the multiple business change queue of synchronization call, also can call each business change queue successively.Composition graphs 3, after synchronous change during business datum, task processor synchronization call queue B, queue C, queue D can change the synchronous of rear business datum to data server B, data server C, data server D; Or after task processor also can change data server B calling queue B business datum synchronous after, then call queue C, queue D successively and respectively the synchronous of rear business datum changed to data server C and data server D.
Step 406: task processor from the foundation order after arriving first, obtains a task identification according to task identification in business change queue successively.
Step 407: task processor searches task identification and the corresponding relation changing daily record, obtains the change daily record corresponding with obtained task identification.
Step 408: task processor, by calling the service interface of second server, carries out service data updating according to change daily record to second server, by the service data updating before changing on second server for changing rear business datum.
Step 409: first server deletes the task identification corresponding with this service data updating from business change queue.
Composition graphs 3, in step 406 to step 409, to carry out synchronizing traffic data to data server B, after task processor calls queue B from business change queue, according to the resume order of task identification from queue B, first task identification 1 is obtained, suppose the corresponding business change 1 of this task identification 1, after then searching the change daily record corresponding with task identification 1, obtain the change daily record of business change 1, from this change daily record, obtain the business datum before changing of business change 1 and change rear business datum; The now service interface of task processor calling data server B, by the business datum before changing of business change 1 and after changing synchronizing traffic data to data server B, be the rear business datum of change by data server B by the service data updating before changing that it stores; After this synchronizing traffic data completes, the task identification 1 in queue B can notification data server A be deleted by task processor.By that analogy, carry out above-mentioned process in queue B successively from task identification 2 to task identification n, thus can by synchronizing traffic data after changes all on data server A to data server B.In addition, consistent with data server B to synchronizing traffic data process after data server C and the change of data server D, do not repeat them here.
Step 410: judge whether to process the task identification in business change queue, if so, then terminate current process, otherwise, return step 406.
Optionally, the embodiment of the present application can also be different according to the reliability of institute's bearer service in first server, and adopt different maintenance modes to business change queue, these maintenance modes can comprise:
When the service reliability that first server carries is higher than the first reliability thresholds arranged, namely when in first server, the reliability requirement of bearer service is higher, can in a database for second server sets up business change queue, be kept at due to database on the memory devices such as hard disk, therefore can ensure can persistence safeguarding of business change queue.Further, when the service reliability that first server carries is higher than the second reliability thresholds arranged, and the second reliability thresholds higher than the first reliability thresholds time, the absolute reliability requiring bearer service in first server is described, therefore when task identification failure is inserted in the business change queue of setting up in database, business datum after change corresponding for this task identification is reverted to business datum before changing, to ensure that all business changes can in the present business change queue of sync-body.
When the service reliability that first server carries is not higher than the first reliability thresholds, namely when in first server, the reliability requirement of bearer service is not high, can in the buffer for second server sets up business change queue, thus can improve business change queue set up speed, and task processor calls processing speed to business change queue.
As seen from the above-described embodiment, the attended operation of business change can be concentrated on the data center at place, the business datum side of change by business data synchronization system, thus alleviate the attended operation of other data centers to business change, and carried out synchronously, the processing load of each data center can being alleviated to business datum after change by task processor unification; Because above-described embodiment can also, according to the difference of service reliability, adopt flexi mode maintenance service to change queue, thus ensure that the persistence of high reliability business is safeguarded.
See Fig. 5, an embodiment block diagram for the application's synchronizing traffic data device:
This device comprises: call unit 510 and lock unit 520.
Wherein, call unit 510, for when will by the change in first server after synchronizing traffic data to second server time, call the business change queue of described second server, at least one task identification is comprised, a business change in the corresponding described first server of each task identification in described business change queue;
Lock unit 520, for according to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
Above-mentioned synchronizing traffic data device can be applied on task processor, and this task processor can be arranged independent of server, also can be integrated in the first server of generation business change.
See Fig. 6, another embodiment block diagram for the application's synchronizing traffic data device:
This device comprises: set up unit 610, generation unit 620, storage unit 630, plug-in unit 640, call unit 650 and lock unit 660.
Wherein, set up unit 610, for setting up business change queue for described second server;
Generation unit 620, for when business change occurs described first server, for daily record and task identification are changed in described business change generation, described change log packet is containing the business datum rear with change of business datum before changing of described business change;
Storage unit 630, for preserving the corresponding relation of described task identification and described change daily record;
Plug-in unit 640, for being inserted in described business change queue by described task identification order;
Call unit 650, for when will by the change in first server after synchronizing traffic data to second server time, call the business change queue of described second server, at least one task identification is comprised, a business change in the corresponding described first server of each task identification in described business change queue;
Lock unit 660, for according to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
In an optional implementation:
Described lock unit 660 can comprise (not shown in Fig. 6):
Mark obtains subelement, for according to task identification in described business change queue from the foundation order after arriving first, obtain each task identification successively; Daily record obtains subelement, for searching described corresponding relation, obtains the change daily record corresponding with the task identification obtained; Data Update subelement, for the service interface by calling described second server, service data updating is carried out to described second server, described service data updating comprises according to described change daily record, by the service data updating before changing on described second server for changing rear business datum.
In another optional implementation:
Described unit 610 of setting up can comprise at least one following subelement (not shown in Fig. 6): first sets up subelement, for when the service reliability that described first server carries is higher than the first reliability thresholds arranged, set up business change queue for described second server in a database; Second sets up subelement, for when the service reliability that described first server carries is not higher than described first reliability thresholds, sets up business change queue in the buffer for described second server.
Further, described device can also comprise (not shown in Fig. 6): inverting units, for when the service reliability that described first server carries is higher than the second reliability thresholds arranged, if task identification failure is inserted in the business change queue of setting up in described database, then business datum after change corresponding for described task identification is reverted to business datum before changing, wherein, described second reliability thresholds is higher than described first reliability thresholds.
In another optional implementation:
Described device can also comprise (not shown in Fig. 6): delete cells, after synchronizing traffic data to described second server after by the change of described business change, from described business change queue, delete the task identification corresponding with described business change.
Above-mentioned synchronizing traffic data device can be applied on task processor, and this task processor is integrated in first server usually.
In said apparatus, the implementation procedure of the function and efficacy of unit specifically refers to the implementation procedure of corresponding step in said method, does not repeat them here.
For device embodiment, because it corresponds essentially to embodiment of the method, so relevant part illustrates see the part of embodiment of the method.Device embodiment described above is only schematic, the wherein said unit illustrated as separating component or can may not be and physically separates, parts as unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of module wherein can be selected according to the actual needs to realize the object of the application's scheme.Those of ordinary skill in the art, when not paying creative work, are namely appreciated that and implement.
There is above-described embodiment visible, when carrying out synchronizing traffic data, by the second server maintenance service change queue that the first server that business datum change occurs is business datum after needs synchronously change, so that task processor is after calling business change queue, according to task identification in business change queue from the foundation order after arriving first, by synchronizing traffic data after the change corresponding with each task identification to second server.Application the embodiment of the present application, the attended operation of business change can be concentrated on the data center at place, the business datum side of change, thus alleviate the attended operation of other data centers to business change, and carried out synchronously, the processing load of each data center can being alleviated to business datum after change by task processor unification.
Those skilled in the art, at consideration specification and after putting into practice invention disclosed herein, will easily expect other embodiment of the application.The application is intended to contain any modification of the application, purposes or adaptations, and these modification, purposes or adaptations are followed the general principle of the application and comprised the undocumented common practise in the art of the application or conventional techniques means.Specification and embodiment are only regarded as exemplary, and true scope and the spirit of the application are pointed out by claim below.
Should be understood that, the application is not limited to precision architecture described above and illustrated in the accompanying drawings, and can carry out various amendment and change not departing from its scope.The scope of the application is only limited by appended claim.
Claims (15)
1. a synchronizing traffic data method, is characterized in that, described method comprises:
When will by the change in first server after synchronizing traffic data to second server time, call the business change queue of described second server, at least one task identification is comprised, a business change in the corresponding described first server of each task identification in described business change queue;
According to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
2. method according to claim 1, is characterized in that, described method also comprises:
For described second server sets up business change queue;
When business change occurs described first server, for daily record and task identification are changed in described business change generation, described change log packet is containing the business datum rear with change of business datum before changing of described business change;
Preserve the corresponding relation of described task identification and described change daily record;
Described task identification order is inserted in described business change queue.
3. method according to claim 2, it is characterized in that, described according to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server, comprising:
According to task identification in described business change queue from the foundation order after arriving first, obtain each task identification successively;
Search described corresponding relation, obtain the change daily record corresponding with the task identification obtained;
Carry out service data updating by the service interface calling described second server to described second server, described service data updating comprises according to described change daily record, by the service data updating before changing on described second server for changing rear business datum.
4. method according to claim 2, is characterized in that, describedly sets up business change queue and comprises for described second server:
When the service reliability that described first server carries is higher than the first reliability thresholds arranged, set up business change queue for described second server in a database;
When the service reliability that described first server carries is not higher than described first reliability thresholds, set up business change queue for described second server in the buffer.
5. method according to claim 4, is characterized in that, described method also comprises:
When the service reliability that described first server carries is higher than the second reliability thresholds arranged, if task identification failure is inserted in the business change queue of setting up in described database, then business datum after change corresponding for described task identification is reverted to business datum before changing, wherein, described second reliability thresholds is higher than described first reliability thresholds.
6., according to the arbitrary described method of claim 1 to 5, it is characterized in that, described method also comprises:
After by the change of described business change after synchronizing traffic data to described second server, from described business change queue, delete the task identification corresponding with described business change.
7. a synchronizing traffic data device, is characterized in that, described device comprises:
Call unit, for when will by the change in first server after synchronizing traffic data to second server time, call the business change queue of described second server, at least one task identification is comprised, a business change in the corresponding described first server of each task identification in described business change queue;
Lock unit, for according to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
8. device according to claim 7, is characterized in that, described device also comprises:
Set up unit, for setting up business change queue for described second server;
Generation unit, for when business change occurs described first server, for daily record and task identification are changed in described business change generation, described change log packet is containing the business datum rear with change of business datum before changing of described business change;
Storage unit, for preserving the corresponding relation of described task identification and described change daily record;
Plug-in unit, for being inserted into described task identification order in described business change queue.
9. device according to claim 8, is characterized in that, described lock unit comprises:
Mark obtains subelement, for according to task identification in described business change queue from the foundation order after arriving first, obtain each task identification successively;
Daily record obtains subelement, for searching described corresponding relation, obtains the change daily record corresponding with the task identification obtained;
Data Update subelement, for the service interface by calling described second server, service data updating is carried out to described second server, described service data updating comprises according to described change daily record, by the service data updating before changing on described second server for changing rear business datum.
10. device according to claim 8, is characterized in that, described unit of setting up comprises at least one following subelement:
First sets up subelement, for when the service reliability that described first server carries is higher than the first reliability thresholds arranged, sets up business change queue in a database for described second server;
Second sets up subelement, for when the service reliability that described first server carries is not higher than described first reliability thresholds, sets up business change queue in the buffer for described second server.
11. methods according to claim 10, is characterized in that, described device also comprises:
Inverting units, for when the service reliability that described first server carries is higher than the second reliability thresholds arranged, if task identification failure is inserted in the business change queue of setting up in described database, then business datum after change corresponding for described task identification is reverted to business datum before changing, wherein, described second reliability thresholds is higher than described first reliability thresholds.
12. according to the arbitrary described device of claim 7 to 11, and it is characterized in that, described device also comprises:
Delete cells, after synchronizing traffic data to described second server after by the change of described business change, deletes the task identification corresponding with described business change from described business change queue.
13. 1 kinds of business data synchronization systems, is characterized in that, described system comprises: task processor, first server and at least one second server, wherein,
Described first server, for changing queue for each described second server maintenance service, comprises at least one task identification in described business change queue, a business change in the corresponding described first server of each task identification;
Described task processor, for when will by the change in first server after synchronizing traffic data to described second server time, call the business change queue of described second server; According to task identification in described business change queue from the foundation order after arriving first, by with the change of business change corresponding to each task identification after synchronizing traffic data to described second server.
14. systems according to claim 13, is characterized in that,
Described first server, also for setting up business change queue for described second server, when business change occurs described first server, for daily record is changed in described business change generation, described change log packet is containing the business datum rear with change of business datum before changing of described business change; For task identification is set up in described business change; Described task identification order is inserted in described business change queue; Preserve the corresponding relation of described task identification and described change daily record.
15. systems according to claim 13 or 14, it is characterized in that, when the quantity of described second server is less than predetermined number, described task processor is integrated in described first server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410277682.0A CN105208060B (en) | 2014-06-19 | 2014-06-19 | Synchronizing traffic data method, apparatus and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410277682.0A CN105208060B (en) | 2014-06-19 | 2014-06-19 | Synchronizing traffic data method, apparatus and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105208060A true CN105208060A (en) | 2015-12-30 |
| CN105208060B CN105208060B (en) | 2019-01-18 |
Family
ID=54955489
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410277682.0A Active CN105208060B (en) | 2014-06-19 | 2014-06-19 | Synchronizing traffic data method, apparatus and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105208060B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107180116A (en) * | 2017-06-28 | 2017-09-19 | 努比亚技术有限公司 | A kind of data synchronizing processing method, mobile terminal and computer-readable recording medium |
| CN107908472A (en) * | 2017-09-30 | 2018-04-13 | 平安科技（深圳）有限公司 | Data synchronization unit, method and computer-readable recording medium |
| CN108415792A (en) * | 2018-01-15 | 2018-08-17 | 阿里巴巴集团控股有限公司 | Disaster tolerance system, method, apparatus and equipment |
| CN109167831A (en) * | 2018-08-31 | 2019-01-08 | 北京航天云路有限公司 | Multi-site user behavior information synchronization method and system |
| CN109634853A (en) * | 2018-11-30 | 2019-04-16 | 平安科技（深圳）有限公司 | Data test method, system, electronic device and computer readable storage medium |
| CN110941623A (en) * | 2019-11-12 | 2020-03-31 | 北京达佳互联信息技术有限公司 | Data synchronization method and device |
| CN113268540A (en) * | 2021-03-26 | 2021-08-17 | 北京视博云信息技术有限公司 | Data synchronization method and device |
| CN113779143A (en) * | 2021-08-20 | 2021-12-10 | 中国邮政储蓄银行股份有限公司 | Double-activity data center and business system |
| CN114422577A (en) * | 2020-10-12 | 2022-04-29 | 腾讯科技（深圳）有限公司 | Method and device for processing service change message |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1482764A (en) * | 2002-09-12 | 2004-03-17 | 深圳市中兴通讯股份有限公司 | Method for synchronisation of master and standby background net management data |
| CN102098342A (en) * | 2011-01-31 | 2011-06-15 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
-
2014
- 2014-06-19 CN CN201410277682.0A patent/CN105208060B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1482764A (en) * | 2002-09-12 | 2004-03-17 | 深圳市中兴通讯股份有限公司 | Method for synchronisation of master and standby background net management data |
| CN102098342A (en) * | 2011-01-31 | 2011-06-15 | 华为技术有限公司 | Transaction level-based data synchronizing method, device thereof and system thereof |
Cited By (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107180116A (en) * | 2017-06-28 | 2017-09-19 | 努比亚技术有限公司 | A kind of data synchronizing processing method, mobile terminal and computer-readable recording medium |
| CN107908472A (en) * | 2017-09-30 | 2018-04-13 | 平安科技（深圳）有限公司 | Data synchronization unit, method and computer-readable recording medium |
| WO2019062182A1 (en) * | 2017-09-30 | 2019-04-04 | 平安科技（深圳）有限公司 | Data synchronization device and method, and computer readable storage medium |
| CN108415792A (en) * | 2018-01-15 | 2018-08-17 | 阿里巴巴集团控股有限公司 | Disaster tolerance system, method, apparatus and equipment |
| CN108415792B (en) * | 2018-01-15 | 2022-04-29 | 创新先进技术有限公司 | Disaster recovery system, method, device and equipment |
| CN109167831A (en) * | 2018-08-31 | 2019-01-08 | 北京航天云路有限公司 | Multi-site user behavior information synchronization method and system |
| CN109634853A (en) * | 2018-11-30 | 2019-04-16 | 平安科技（深圳）有限公司 | Data test method, system, electronic device and computer readable storage medium |
| CN110941623A (en) * | 2019-11-12 | 2020-03-31 | 北京达佳互联信息技术有限公司 | Data synchronization method and device |
| CN114422577A (en) * | 2020-10-12 | 2022-04-29 | 腾讯科技（深圳）有限公司 | Method and device for processing service change message |
| CN113268540A (en) * | 2021-03-26 | 2021-08-17 | 北京视博云信息技术有限公司 | Data synchronization method and device |
| CN113779143A (en) * | 2021-08-20 | 2021-12-10 | 中国邮政储蓄银行股份有限公司 | Double-activity data center and business system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105208060B (en) | 2019-01-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105208060A (en) | Service data synchronization method, service data synchronization device and service data synchronization system | |
| US9025602B2 (en) | Data redistribution in data replication systems | |
| US9009215B2 (en) | Methods, devices and systems for dynamically managing memberships in replicated state machines within a distributed computing environment | |
| CN108121782B (en) | Distribution method of query request, database middleware system and electronic equipment | |
| US9367261B2 (en) | Computer system, data management method and data management program | |
| EP2954424B1 (en) | Method, device, and system for peer-to-peer data replication and method, device, and system for master node switching | |
| CN110673941B (en) | Migration method of micro-services in multiple computer rooms, electronic equipment and storage medium | |
| US11514077B2 (en) | Replication event ordering using an external data store | |
| JP2007503050A5 (en) | ||
| CN106709066B (en) | Data synchronization method and device | |
| CN110083651B (en) | Data loading method and device | |
| US9141677B2 (en) | Apparatus and method for arranging query | |
| CN108696581A (en) | Caching method, device, computer equipment and the storage medium of distributed information | |
| JP6975153B2 (en) | Data storage service processing method and equipment | |
| CN103530395B (en) | Data tracing method and device | |
| CN108228812B (en) | Self-adaptive main node switching method and device | |
| CN104462342B (en) | database snapshot synchronization processing method and device | |
| CN109859068B (en) | Power grid data real-time synchronization system based on resource pool technology | |
| CN104793981A (en) | Online snapshot managing method and device for virtual machine cluster | |
| CN106791932A (en) | Distributed trans-coding system, method and its device | |
| CN109413225B (en) | MAC table item processing method and equipment | |
| CN110442645A (en) | Data index method and device | |
| US10831561B2 (en) | Method for changing allocation of data using synchronization token | |
| RU2698766C1 (en) | Method and device for transmitting, sending and receiving information | |
| CN109471894B (en) | Novel system and method for uniformly storing distributed files and objects |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20191209 Address after: P.O. Box 31119, grand exhibition hall, hibiscus street, 802 West Bay Road, Grand Cayman, Cayman Islands Patentee after: Innovative advanced technology Co., Ltd Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Co., Ltd. |