CN106302625A - Data-updating method, device and related system - Google Patents
Data-updating method, device and related system Download PDFInfo
- Publication number
- CN106302625A CN106302625A CN201510363437.6A CN201510363437A CN106302625A CN 106302625 A CN106302625 A CN 106302625A CN 201510363437 A CN201510363437 A CN 201510363437A CN 106302625 A CN106302625 A CN 106302625A
- Authority
- CN
- China
- Prior art keywords
- list
- copy
- server
- replica server
- attribute
- 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
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/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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/21—Design, administration or maintenance of databases
- G06F16/219—Managing data history or versioning
-
- 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/23—Updating
-
- 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/25—Integrating or interfacing systems involving database management systems
-
- 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/273—Asynchronous replication or reconciliation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
- G06F3/0614—Improving the reliability of storage systems
- G06F3/0617—Improving the reliability of storage systems in relation to availability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/065—Replication mechanisms
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
- G06F3/067—Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- 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
A kind of data-updating method disclosed by the invention, device and related system, wherein, described data-updating method includes: receive the response message after data trnascription has updated in every described replica server;When the response message quantity received in when updated is less than the total quantity of described replica server, it is revised as continuing more new state by copy information corresponding for the replica server not sending response message;When not receiving the response message that the described replica server continuing to update sends in the default continuation renewal time yet, described copy information is deleted from described copy list;Update the list attribute value of described copy list, and this list attribute value is sent in central server.Compared with prior art, technical solution of the present invention can reduce, on the basis of reducing the shake of I/O performance, the frequency writing data to central server, and then can reduce the pressure of central server, improves system availability.
Description
Technical field
The present invention relates to technical field of distributed memory, more specifically, relate to a kind of data-updating method, device and phase
Pass system.
Background technology
Along with all trades and professions of network penetration society, network backend needs the data volume stored increasing, and usual every day is all
A large amount of data needing storage can be produced.Traditional network storage is for be centrally stored in data in a station server, not only
Cause storage load, and there is potential safety hazard.In order to meet the demand of mass data storage, the most commonly used
Storage mode is distributed storage.Distributed storage refers to, stores data as multiple copy, and each data trnascription is corresponding
Being stored in a replica server, share storage load by multiple stage replica server, that can improve storage can simultaneously
By property.
Owing to data trnascription is stored in multiple stage replica server, client maintenance a copy list, this copy list
In have recorded each copy information of data, and the replica server address that every copy information is corresponding, when data update,
Client needs all replica server addresses of storage in copy list to send more newly requested, and all data trnascriptions are same
Time be updated, wherein, after the data trnascription in every replica server has updated, this replica server is to client
Send the response message including data trnascription version number.And when read/write data, the most any one or several copies
Server fail, network failure or disk failure etc. cause I/O performance to shake, and all can cause part Copy Service
Data trnascription in device cannot be successfully updated, thus causes data to be updated successfully.In order to solve this problem, existing
Data-updating method is, client is sent to after each replica server start timing by more newly requested for data, if preset
In the renewal time, when client receives quantity X of response message more than or equal to predetermined threshold value M, it is considered as data more
New success, using X the copy being updated successfully as effective copy.Wherein, predetermined threshold value M is stored less than data trnascription
Replica server total quantity N, M, N and X are natural number.So, system just can tolerate (N-M) platform Copy Service
The performance shake of device.
Due to the client copy list by data stored in memory, if client crashes, the data that it is stored will be complete
Portion loses, and causes client cannot determine the current version number of data, thus cannot continue more new data.And again carry out
When data update, client has only to send more newly requested to the replica server that data trnascription is current version number, therefore,
The replica server not being updated successfully by data trnascription by current version number is needed to get rid of, when client occurs to crash,
Need to recover the current version number of data.Existing processing mode is, when X is less than N, the most secondary by X
The current version number of this correspondence is stored in central server, after client crashes, by current version from central server
This number reading, thus the replica server of effective copy and correspondence thereof is determined by current version number, will not be updated successfully
Server corresponding to data trnascription get rid of.
In view of the shake of I/O performance is relatively big on the impact of system, in order to ensure the stationarity of system, conventional way is to pass through
Weaken the shake of I/O performance by updating the shorter of set of time as far as possible, so on the one hand can reduce generation I/O performance and tremble
Dynamic probability, on the other hand, it is possible to before producing the shake of I/O performance, complete data update.But, update the time more
Short, when every secondary data updates, produce that not updated the probability of data trnascription the biggest, and then need more frequently to
Central server write data, thus cause storage pressure and the performance bottleneck of central server, reduce system availability.
Summary of the invention
In view of this, the embodiment of the present invention provides a kind of data-updating method, device and related system, is reducing I/O
On the basis of shaking, it is possible to reduce the frequency to central server write data such that it is able to reduce central server
Pressure, improves system availability.
First aspect, embodiments provides a kind of data-updating method, including: stored in copy list
After replica server transmission is more newly requested, receive the letter of the response after data trnascription has updated in every described replica server
Breath;When the response message quantity received in the default renewal time is less than the total quantity of described replica server, sound will not sent
The copy information answering the replica server of information corresponding is revised as continuing more new state;When receiving not yet in the default continuation renewal time
During to the response message of the replica server transmission of described continuation renewal, described copy information is deleted from described copy list;
Update the list attribute value of described copy list, and the described list attribute value after updating sends and is stored in central server
In.
In the first possible implementation of first aspect, in receiving every described replica server, data trnascription updates
Before response message after completing, also include: generate data more newly requested more newly requested with attribute;Wherein, described attribute updates
Request is the solicited message of more new version number;The data trnascription server storing data trnascription respectively in described copy list sends
Described data are more newly requested;In described copy list, the attribute replica server of attribute information storage sends described attribute more respectively
Newly requested.
In conjunction with above-mentioned first aspect, in the implementation that the second is possible, when the response letter received in the default renewal time
When breath quantity is less than the total quantity of described replica server, also include: the version number according to copy corresponding to described response message is raw
Become attribute more newly requested;It is separately sent to more newly requested for described attribute in attribute replica server.
In conjunction with above-mentioned first aspect, in the implementation that the third is possible, in the list attribute value updating described copy list
Afterwards, before the described list attribute value after updating sends and is stored in central server, also include: after updating
Described list attribute value sends respectively and stores in the replica server that described copy list is stored.
In conjunction with above-mentioned first aspect, in the 4th kind of possible implementation, also include: obtain from described central server
History list property value and history replica server address, wherein, described history replica server address is for according to predetermined period institute
The replica server address of storage in the copy list sent;Respectively to the Copy Service that described history replica server address is corresponding
Device sends Query Information;Receive described replica server and respond the pre-stored list property value that described Query Information is sent;Work as institute
When stating pre-stored list property value more than or equal to described history list property value, address corresponding for described replica server is deposited
Storage is in described copy list.
In conjunction with above-mentioned first aspect, in the 5th kind of possible implementation, by address corresponding for described replica server
After being stored in described copy list, also include: obtain the version number in every described copy information;By described version number
The data trnascription that high copy information is corresponding is defined as effective copy;Described version number is believed less than the copy of described top version number
The copy information that breath is corresponding is deleted from described copy list;The list attribute updating described copy list is worth to new list attribute
Value;Described new list attribute value is sent and is stored in described central server.
Second aspect, the embodiment of the present invention additionally provides a kind of data update apparatus, including: receiver module, for pair
The replica server that stored in this list send more newly requested after, receive data trnascription in every described replica server and update
Response message after completing;Status modifier module, for the response letter received within the default renewal time when described receiver module
When breath quantity is less than the total quantity of described replica server, copy information corresponding for the replica server not sending response message is repaiied
Change into continuing more new state;Removing module, for not receiving described yet when described receiver module within the default continuation renewal time
During the response message that the replica server continuing to update sends, described copy information is deleted from described copy list;Update mould
Block, after described copy information is deleted from described copy list by described removing module, updates the list of described copy list
Property value;Sending module, for sending the list attribute value that described more new module is updated and be stored in central server.
In the first possible implementation of second aspect, also include: generation module, wherein, described generation module,
For generating, data are more newly requested and attribute is more newly requested;Wherein, described attribute is more newly requested is the solicited message of more new version number;
Described sending module, the data trnascription server being additionally operable to store in described copy list respectively data trnascription sends described data
More newly requested;In described copy list, the attribute replica server described attribute of transmission of attribute information storage is more newly requested respectively.
In conjunction with above-mentioned second aspect, in the implementation that the second is possible, described generation module, it is additionally operable to according to described
It is more newly requested that the version number of the copy that response message is corresponding generates attribute.
In conjunction with above-mentioned second aspect, in the implementation that the third is possible, described sending module, it is additionally operable to after renewal
Described list attribute value send respectively and store in the replica server that described copy list is stored.
In conjunction with above-mentioned second aspect, in the 4th kind of possible implementation, also include: acquisition module and memory module, its
In, described acquisition module, for obtaining history list property value and history replica server address from described central server,
Wherein, the replica server ground that described history replica server address is storage in the copy list that sent according to predetermined period
Location;Described sending module, is additionally operable to replica server corresponding to described history replica server address respectively and sends Query Information;
Described receiver module, is additionally operable to receive described replica server and responds the pre-stored list property value that described Query Information is sent;
Described memory module, for when described pre-stored list property value is more than or equal to described history list property value, by described
The address that replica server is corresponding is stored in described copy list.
In conjunction with above-mentioned second aspect, in the 5th kind of possible implementation, also include determining module, wherein, described in obtain
Delivery block, is additionally operable to obtain the version number in every described copy information;Described determine module, for by the highest for described version number
Data trnascription corresponding to copy information be defined as effective copy;Described removing module, is additionally operable to described version number less than described
The copy information that the copy information of top version number is corresponding is deleted from described copy list;Described more new module, is additionally operable to update
The list attribute of described copy list is worth to new list attribute value;Described sending module, is additionally operable to update described copy list
List attribute is worth to new list attribute value.
The third aspect, the embodiment of the present invention additionally provides a kind of data update system, including client, replica server and in
Central server, wherein, described client is as described in second aspect;Described replica server, is used for receiving described client
The list attribute value sent;Described central server, for receiving the list attribute value that described client sends.
In the first possible implementation of the third aspect, described central server, it is additionally operable to described Copy Service
Device sends and obtains copy information request, and receives the copy information that described replica server sends, according to described copy information
Determine address list;The list attribute value stored and address list are sent to described client;Described replica server,
Be additionally operable to receive the acquisition copy information request that described central server sends, and described copy information is sent to described in
Central server.
From above technical scheme, the problem low in order to solve system availability, the data that the embodiment of the present invention is provided
Update method, device and related system, the replica server stored in copy list respectively in client sends more newly requested
After, receive the response message after data trnascription has updated in every replica server, when the response received in the default renewal time
When information content is less than replica server total quantity, illustrating to exist the replica server not being updated successfully, now, the present invention implements
In example, this replica server is not got rid of, but copy information corresponding for the replica server not sending response message is revised
For continuing more new state, this replica server is kept to continue to update.If within the default continuation renewal time, still do not received
The response message that the replica server continuing to update sends, then by copy information corresponding for this replica server from copy list
Delete, thus this data trnascription is got rid of from the data trnascription being updated successfully.Copy list is changed owing to deleting copy information
List attribute, the list attribute value of the embodiment of the present invention more latest copy list, and will update after list attribute value send and deposit
Storage is in central server.Compared with prior art, during the replica server that interior existence is not updated successfully when updated, it is not necessary to
This replica server is got rid of, it is therefore not necessary to current version number is stored in central server.And when getting rid of replica server
Time, the change of copy list will necessarily be caused, therefore, list, only when copy list changes, is belonged to by the embodiment of the present invention
Property value store central server such that it is able to reduce I/O performance shake on the basis of, reduce write number to central server
According to frequency, and then the pressure of central server can be reduced, improve system availability.
Accompanying drawing explanation
In order to be illustrated more clearly that the embodiment of the present invention or technical scheme of the prior art, below will be to required in embodiment
Accompanying drawing to be used is briefly described, it should be apparent that, the accompanying drawing in describing below is only some enforcements of the present invention
Example, for those of ordinary skill in the art, on the premise of not paying creative work, it is also possible to attached according to these
Figure obtains other accompanying drawing.Shown in accompanying drawing, above and other purpose, feature and the advantage of the present invention will become apparent from.
The part that reference instruction identical in whole accompanying drawings is identical.The most deliberately draw attached by actual size equal proportion scaling
Figure, it is preferred that emphasis is illustrate the purport of the present invention.
The method flow diagram of the data-updating method that Fig. 1 provides for the embodiment of the present invention;
The mutual schematic diagram of information that Fig. 2 recovers for the data that the embodiment of the present invention provides;
The method flow diagram of the another kind of data-updating method that Fig. 3 provides for the embodiment of the present invention;
The structural representation of the data update apparatus that Fig. 4 provides for the embodiment of the present invention;
The structural representation of the data update system that Fig. 5 provides for the embodiment of the present invention.
Detailed description of the invention
Owing to client maintenance the copy list of data, copy list have recorded the copy information that each copy is corresponding,
When client needs to get rid of the replica server not being updated successfully, can believe by deleting copy corresponding to replica server
The mode of breath is carried out.Therefore, in order to solve the technical problem that prior art exists, the technical scheme of the embodiment of the present invention is led to
Cross and utilize this characteristic to realize.
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete
Description, it is clear that described embodiment is only a part of embodiment of the present invention rather than whole embodiments.Base
Embodiment in the present invention, it is all that those of ordinary skill in the art are obtained under not making creative work premise
Other embodiments, broadly fall into the scope of protection of the invention.
In prior art, the renewal time I/O performance to system and the frequency to central server storage data all can be produced
Life directly affects, but, update the time the longest, although the frequency to central server storage data can reduce, but I/O
The impact that performance jitter on data updates can increase;And the time that updates is the shortest, although the shadow of I/O performance can be weakened as far as possible
Ring, but be likely to result in and store operation frequently, cause storage pressure and the performance bottleneck of central server.That is, I/O
The storage pressure of performance and central server is unable to reach balance, thus can reduce the availability of system.
Therefore, the method flow diagram of the data-updating method that Fig. 1, Fig. 1 provide is referred to for the embodiment of the present invention.Described side
Method comprises the following steps:
Step S101, after the replica server transmission stored in copy list is more newly requested, receives every described pair
Response message after data trnascription has updated in book server.
Wherein, owing to distributed storage stores data as multiple data trnascription, each copy correspondence is stored in a copy
In server, for the ease of management, client is by safeguarding that copy and the replica server of data are managed by copy list
Reason.Wherein, copy row tableau format is as shown in table 1, and every copy information all includes List Identification, replica server ground
The information such as location, copy version number and copy state.Certainly, table 1 is only used to illustrate copy row tableau format
The example provided, during actual storage, the copy amount corresponding to each data can not be 3, the embodiment of the present invention this
Place is no longer described in detail.
Table 1
List Identification | Replica server address | Copy version number | Copy state |
1 | Address 1 | 5.0 | Normally |
2 | Address 2 | 5.0 | Normally |
3 | Address 3 | 5.0 | Continue to update |
It should be noted that the copy state in copy list is in the replica server that respective copies server address is corresponding
The state of copy, therefore, it can the command information according to client sends and adjusts at any time.Such as, in the present embodiment, when
Client is after the replica server transmission of address 1 correspondence is more newly requested, and in replica server, the copy of storage needs root
Being updated according to more newly requested, client can be by the copy status modifier of address 1 correspondence in renewal;When renewal completes,
Copy state is updated to normally.Certainly, when the copy state in replica server is other states, client is also entered
Row correspondence change, this is repeated no more by the present invention.
When data update, client generates more newly requested, and to be sent to replica server address corresponding by more newly requested
In replica server.Replica server receive more newly requested after, read more newly requested in version number, and with stored
The version number of data trnascription contrasts, when the version number of the data trnascription stored is less than read version number, according to more
The data trnascription that newly requested renewal is stored, in the disk of the data that will update write replica server, after having updated, to
Client sends the response message being updated successfully, to notify that this data trnascription of client is updated successfully.Therefore, the embodiment of the present invention
In, response message can be a signal not comprising any data, and the present invention is without limitation.
Owing to the copy in replica server is the most updated, corresponding version number should also be as updating, and therefore, client receives pair
After the response message that book server sends, read the replica server address that response message is corresponding, according to replica server address
In copy list, search the copy version number of correspondence, corresponding copy version number is revised as current version number, and will be corresponding
Copy status modifier is normal.
Additionally, distributed storage can arrange multiple client, each client is all corresponding with multiple replica servers,
But, the data that different clients is stored are different, and the complete phase of method and steps that in each client, data update
With, here is omitted for the present invention.But, in distributed storage, different clients may use identical replica server,
Therefore, when one of them replica server is the replica server of another one or several client simultaneously, in order to enable
Enough to sending more newly requested client transmission response message, while reception is more newly requested, set up and relative client
Communication linkage, after Replica updating completes, the communication linkage that multiplexing is set up such that it is able to response message is led to by this
Letter link is sent to corresponding client.
Step S102, when the response message quantity received in the default renewal time is less than the total quantity of described replica server,
It is revised as continuing more new state by copy information corresponding for the replica server not sending response message.
Wherein, according to prior art, in order to reduce the shake of I/O performance, the response message received within the renewal time
Quantity i.e. think be updated successfully equal to predetermined threshold value, and the time that updates is configured in advance.Generally, set renewal
Time is the time that predetermined threshold value copy can update, and can be set according to historical experience value.Therefore, logical
In the case of Chang, the copy amount that can update in presetting the renewal time is at least the quantity of predetermined threshold value, say, that
In the present embodiment, the response message quantity received in presetting the renewal time includes less than the situation of replica server total quantity: ring
Answer the quantity of information more than or equal to predetermined threshold value.Certainly, in the case of extremely particularly, such as grid card pauses,
The response message quantity received in the renewal time is likely less than predetermined threshold value, and now, client enters waiting state, until
The quantity of the response message received is equal to predetermined threshold value.
In the embodiment of the present invention, the interior response message quantity that receives is more than or equal to predetermined threshold value when updated, less than pair
During book server sum, by copy status modifier corresponding for the replica server not responded for continuing more new state, and start
Record continues the renewal time.In continuing the renewal time at the copy not being updated successfully, this pair being updated successfully
This may need to carry out lower secondary data renewal, and therefore, client can send to the replica server not sending response message
Asynchronous write order, transfers this replica server to backstage asynchronous write, sends out replica server formation two with being updated successfully
Thread, thus avoid the process of the two to influence each other.
In the present embodiment, when default renewal time memory is at the copy not updated, not by pair corresponding for this copy
Book server is got rid of, but changes the state of this copy, provides the chance continuing to update for this copy such that it is able to reduce
Probability to central server write data.
Step S103, when not receiving the response that the described replica server continuing to update sends in the default continuation renewal time yet
During information, described copy information is deleted from described copy list.
Wherein, according to foregoing description, in continuing the renewal time, this copy being updated successfully may enter
Row is next or updates more times, causes the copy continuing to update to fall behind current version one even more than version.In order to protect
Holding version concordance, reduce operating process, in continuing the renewal time, if again carrying out data renewal, client depends on
So by more newly requested this replica server that is sent to, and the replica server continuing more new state can be in when continuing to update
It is considered as continuing to be updated successfully when interior renewal is to current highest version, sends response message to client the most again.Such as,
Version number after this updates is 5.0, and the replica server of address 3 correspondence does not sends response letter within the default renewal time
Breath, by the copy status modifier of its correspondence for continuing more new state, when in address 3, the continuation of the copy of corresponding storage updates
In, version number be 5.0 copy again update, the version number after renewal is 5.5, now, the corresponding storage in address 3
Copy continue to be updated to send response message to client again during the data that version number is 5.5.
Continuing in the renewal time if preset, being in and continuing the replica server of more new state and still do not send response message,
Then illustrate that the copy continuing more new state is not updated successfully, for keeping the concordance of copy version, the present invention in copy list
This replica server is got rid of by embodiment by being deleted by copy information corresponding for this replica server.Such as, address 3 is right
The copy that should store fails to be updated to the version of version number 5.5 correspondence in continuing the renewal time, then client will be deleted
The copy information of address 3 correspondence, thus this copy is abandoned.
It should be noted that carry out effective copy recovery for the ease of client, in central server, also storage has and client
The address list of the replica server that end copy list is corresponding, when client needs to carry out data recovery, can be from address
List obtains the address of replica server, thus obtains the copy version in the replica server of correspondence.Due to client
Copy list often change, and in central server, storage has address list corresponding to all clients of distributed system,
If the ensuring that central server is completely the same with the replica server address in client, the copy in any one client
List is changed once, and central server is required to update primary address list, then central server will always be in data
The state updated, causes and stores pressure greatly, therefore, in order to the address list upgraded in time in central server,
And reducing the storage pressure of central server, central server, with the regular hour as cycle, periodically takes to all of copy
Business device sends and obtains copy information order, and locally stored all copy informations are sent to by replica server according to this order
Central server, central server can carry out corresponding amendment according to the information the received address list to being stored.
Step S104, updates the list attribute value of described copy list, and the described list attribute value after updating sends and deposits
Storage is in central server.
Wherein, in the embodiment of the present invention, copy list being provided with list attribute value, list attribute value is used for identifying copy
The attribute of list, copy list often changes once, and list attribute value updates once.Due in data updating process, secondary
This list is it may happen that repeatedly change, and for the clear and definite change representing copy list, list attribute value could be arranged to
The mode of timestamp, or be labeled by monotonically increasing Digital ID, the embodiment of the present invention is without limitation.
Copy list is often changed once, and list attribute value can be a certain amount of with monotonic increase on original basis such that it is able to clear and definite
Represent the change information of copy list.In the present embodiment, when client deletes the part copy information in copy list,
Copy order in copy list is caused to change, therefore, the list attribute value of more latest copy list.Due to copy list
Change, illustrate that the copy version number in former copy list is inconsistent, carry out data after crashing for the ease of client extensive
Multiple, the embodiment of the present invention will update after list attribute value, and the replica server address of storage in copy list after updating
Send and store in central server.
Such as, after being deleted by the copy information of corresponding for address 3 in copy list storage, in copy list, the copy information of storage subtracts
Few, copy list changes, it is assumed that before copy list change, list attribute value is a10, then delete the pair of address 3 correspondence
After this information, list attribute value is updated to a11, and address 1, address 2 are sent with a11 and are saved in central server
In.
Additionally, due to the copy information corresponding to copy that will be unable to update is after copy list is deleted, this copy still exists
Continue to update, when, after this Replica updating success, its version number is identical with the version number of effective version, and the copy that this copy is corresponding
Information has been not stored in copy list, and when client carries out data recovery, is only identified by version number, may
Identification mistake can be caused, the copy information deleted is re-added in copy list.Therefore, in order to clearly store
Copy information in copy list, when client updates list attribute value, first, the list attribute value after updating is respectively
It is sent in the replica server of current copy list storage, with by list attribute this replica server of value identification after updating
Copy whether should be stored in copy list, then, then will update after list attribute value send and store center service
In device.
The technical scheme of the present embodiment, recovers to provide multiple basis of characterization for data such that it is able to after client crashes,
Fast and accurately copy information corresponding for effective copy is identified, and return to client.
By the present embodiment it can be seen that data-updating method described in the embodiment of the present invention, when updated in exist not
During the replica server being updated successfully, it is not necessary to this replica server is got rid of, it is therefore not necessary to current version number is stored in center
In server.And when getting rid of replica server, the change of copy list will necessarily be caused, therefore, the embodiment of the present invention only exists
When copy list changes, list attribute value is stored central server such that it is able to reducing the shake of I/O performance
On the basis of, reduce the frequency writing data to central server, and then the pressure of central server can be reduced, improve system
Availability.
Above-described embodiment describes the present invention processing method when data update in detail, seen from the above description, in order to
Effective copy can be recovered after crashing by client, and list attribute value stores central server, and center service
Device updates the replica server address list stored according to predetermined period.In order to make those skilled in the art more clearly
Understanding technical scheme, on the basis of above-described embodiment, the data that client is described in detail below were recovered
Journey.
The data that referring to Fig. 2, Fig. 2 provides for the embodiment of the present invention recover the mutual schematic diagram of information.When client crashes heavy
Qi Hou, first, performs step 01, and client sends acquisition information to central server.Wherein, this acquisition information includes visitor
The identification information of family end.After central server receives this acquisition information, search and this client pair according to client identification information
The history list property value answered and history replica server address, and perform step 02, by history list property value and history copy
Server address is sent to this client.Wherein, history list property value is that client is sent to central server for the last time
List attribute value, history replica server address is the address list that client is sent to central server for the last time.
Step 03, the replica server transmission Query Information that client is corresponding to history replica server address;Step 04,
Replica server response Query Information, is sent to client by the version number of the current list property value and current copy;Step
05, the current list property value is compared by client respectively with history list property value.
Seen from the above description, the address list in central server updates according to predetermined period, and the duration of predetermined period may
The time interval updated more than data, when being engraved within the cycle updating address list when renewal list attribute value, history is secondary
Can comprise the replica server address that the copy abandoned is corresponding in book server address, what the copy that abandons was corresponding works as prostatitis
Table Properties value is less than history list property value, and therefore, client can be by the current list property value less than history list property value
Replica server is got rid of.
Such as, history list property value is a10, is updated delete the copy information of address 3 correspondence by client after, and
Address list one minute left in central server reaches next update cycle, then history replica server address Zhong Bao
Containing the replica server address of address 3 correspondence, and the current list property value of the replica server of address 3 correspondence is a09,
Therefore, the copy information of corresponding for address 3 storage is got rid of.
Additionally, after updating list attribute value, this list attribute value is first separately sent to the pair that copy list is corresponding by client
In book server, the most again this list attribute value is sent to central server, if the list attribute that client is after updating
Value crashes after being sent to replica server end, then the list attribute value after updating cannot be sent to central server, then go through
History list attribute value is likely less than the current list property value that part replica server is corresponding.Now, by big for the current list property value
Replica server in history list property value lists copy list in.
Such as, when list attribute value is updated to a11, client crashes after a11 is sent to replica server, then work as prostatitis
Table Properties value belongs to copy list more than the replica server of history list property value a10, the current list property value less than or etc.
Replica server in a10 is the replica server that the copy being excluded is corresponding.
Additionally, after list attribute value is sent to central server by client, again or more times carry out data more
Newly, the last time in data updating process, some or several replica server are in visitor in the continuation renewal time
Family end crashes, and list attribute value does not update, but but creates the new copy needing to get rid of.Now, will be current
List attribute value is listed in copy list equal to the replica server of history list property value, obtains every pair in copy list
The current version number that this information is corresponding, and copy the highest for current version number is defined as effective copy, delete current version
Number less than the copy information of top version number, and again update list attribute and be worth to new list attribute value, then perform step
Rapid 06, this new list attribute value is sent and stores central server.
Such as, history list property value is a10, and it is 5.5 that list attribute value is updated to the version number of effective copy during a10,
Client has carried out again two secondary data renewals afterwards, and when data update for the first time, corresponding version number is 5.7, for the second time
When data update, corresponding version number is 6.0.After the default renewal time that second time data update, address 5 is deposited
The copy of storage is in and continues more new state, now, and client power down, and the copy version number of the corresponding storage in address 5 is 5.7.
So, the copy list recovering to obtain according to list attribute value includes the copy information of address 5 correspondence.Then right then,
Ratio copy version number corresponding in copy list, the copy that can obtain version number 6.0 correspondence is effective copy, therefore,
The copy information of address 5 correspondence is deleted, list attribute value is updated to a11, and is sent to central server.
As shown from the above technical solution, the embodiment of the present invention is on the basis of the frequency reduced to central server storage data
On, still can by list attribute value and current version number by data accurately and fast return to client, thus
On the basis of not affecting other performance of system, it is possible to well reduce storage pressure and the performance bottleneck of system.
Additionally, from above-described embodiment, in order to ensure that what data updated is normally carried out, the copy amount updated is arranged
There is predetermined threshold value.And in data updating process, may need to update for several times continuously within a period of time, due to different secondary
The I/O performance of book server is different, when data update the most for several times, it is likely that in there will be the default renewal time, nothing is secondary
This renewal, to the situation of highest version, does not i.e. have effective copy to produce.If now client crashes, then cannot be by number
According to recovering to determine the currently active copy, and then cannot be carried out the follow-up renewal of data, therefore, in prior art, preset
The quantity set of threshold value is the half more than copy total quantity, and such as, copy total quantity is 2N+1, then predetermined threshold value is
Little for N+1.But, such setting reduces the I/O performance shake that system can be tolerated, thus reduces system
Availability, therefore, on the basis of above-described embodiment, the embodiment of the present invention additionally provides the second of data-updating method
Embodiment.
Owing to the present embodiment is to supplement above-described embodiment, therefore, part same as the previously described embodiments in the present embodiment,
May refer to the description of above-described embodiment, the present embodiment repeats no more.
Refer to the method flow diagram of the another kind of data-updating method that Fig. 3, Fig. 3 provide, described side for the embodiment of the present invention
Method comprises the following steps:
Step S201: generate data more newly requested more newly requested with attribute.
Wherein, in order to increase the I/O performance shake that system can be tolerated, improve the availability of system, pre-in the present embodiment
The attribute copy of data is first set, described attribute copy only comprises version number corresponding to effective copy and the row of copy list
Table Properties value, each attribute copy correspondence is stored in an attribute replica server.In embodiments of the present invention, attribute
Copy can replace data trnascription to participate in the determination of effective copy, and in copy list, storage has the copy corresponding with attribute copy
Information, its update mode, storage mode are identical with data trnascription, and this is repeated no more by the embodiment of the present invention.
It should be noted that in the present embodiment, each data can be correspondingly arranged at least one attribute copy, the present invention couple
This does not limits.In a preferred exemplary of the present invention, it is assumed that data trnascription sum is 2N+1, predetermined threshold value is N+1,
N number of attribute copy so can be set.
Due to the corresponding two class copies of the copy information in copy list, and attribute copy is stored be data version number and
The list attribute value of copy list, therefore, when data update, it is more newly requested that client corresponding can generate two classes, a kind of
It is that data are more newly requested, including the data message updated and version number;Another kind is that attribute is more newly requested, updates with data
Request is compared, and does not include the data message updated, and other information and dates are the most newly requested identical.
In the present embodiment, by setting up the attribute copy of data, by increasing capacitance it is possible to increase the I/O performance shake that system can be tolerated,
Using attribute copy as the copy determining effective copy, by increasing capacitance it is possible to increase produce the probability of effective copy such that it is able to improve system
The availability of system.
Step S202, the data trnascription server storing data trnascription respectively in described copy list sends the renewal of described data
Request;In described copy list, the attribute replica server described attribute of transmission of attribute information storage is more newly requested respectively.
Wherein, from the description of above-described embodiment, copy information includes List Identification and replica server address, this reality
Execute in example, can be distinguished the character of copy corresponding to this copy information by List Identification, then by corresponding more newly requested
It is sent to the replica server address that corresponding List Identification is corresponding.
Such as, the List Identification that data trnascription is corresponding is " a1, a2 ", the List Identification that attribute copy is corresponding be " b1,
B2 ", after client generation two kinds is more newly requested, it is separately sent to more newly requested for data in List Identification with " a "
Replica server address, be sent in List Identification the replica server address with " b " by more newly requested for attribute.
Certainly, above are only a preferred exemplary of the present invention, in the embodiment of the present invention, it is also possible in other ways will make
The copy information that data trnascription is corresponding with attribute copy indicates, and the present invention is without limitation.
Step S203, receives the response message after data trnascription has updated in every described replica server.
Wherein, similar with the mode that data trnascription updates, after attribute replica server reception attribute is more newly requested, reading attributes is more
Current version number in newly requested, and whether the version number that comparison is stored is less than current version number, if it is lower, will be stored
Version number be updated to current version number, and send response message to client.
Step S204, when the response message quantity received in the default renewal time is less than the total quantity of described replica server,
It is revised as continuing more new state by copy information corresponding for the replica server not sending response message.
Wherein, seen from the above description, when client receive response message quantity be predetermined threshold value time, then it is assumed that data update
Success, in the present embodiment, response message includes response message and the response message of attribute replica server of data trnascription server.
Step S205, when not receiving the response that the described replica server continuing to update sends in the default continuation renewal time yet
During information, described copy information is deleted from described copy list.
Step S206, updates the list attribute value of described copy list, and the described list attribute value after updating sends and deposits
Storage is in central server.
Wherein, after client updates list attribute value, the list attribute value after updating equally sends and stores copy
In attribute replica server corresponding in list, here is omitted for the present invention.
It should be noted that data trnascription is updated by foregoing description and attribute Replica updating is performed by a thread, the present invention
The technical scheme of embodiment is not limited to this, wherein, generates attribute more newly requested in step S201, and by attribute in step S202
The attribute replica server of more newly requested transmission, can be updated with data trnascription and is held by two threads after step s 204
OK.Concrete, by more newly requested for the data data trnascription server that is sent to, and receive the response letter that data trnascription server sends
Breath, when the response message quantity received within the default renewal time is less than data trnascription server sum, generating attribute renewal please
Ask, and be separately sent to attribute replica server by more newly requested for attribute.The embodiment of the present invention is without limitation.
Owing to the present embodiment being additionally arranged attribute copy, and when client receives data trnascription and the response message of attribute copy
When quantity is more than or equal to predetermined threshold value, it is believed that data are updated successfully, thus add the I/O performance shake that can tolerate, it is possible to
The availability of raising system.
Additionally, in the present embodiment, the process that client carries out data recovery is similar to the aforementioned embodiment, the mutual process of information is also
Similar to the aforementioned embodiment, here is omitted for the present invention.
Owing to introducing the attribute copy of data in the present embodiment, and attribute copy only includes effective version number and the list of data
Property value, therefore, even if data update the most for several times, the speed of attribute Replica updating is also very fast, so, as long as having one
Attribute Replica updating in individual attribute replica server the most i.e. can determine that the version number of effective version.When client number
According to when recovering, as long as having the version number of a data trnascription equal to the version number of attribute copy in copy list, can will be somebody's turn to do
Data trnascription is defined as effective copy.
According to foregoing description, the data-updating method that the embodiment of the present invention is provided, in client institute in copy list respectively
Storage replica server send more newly requested after, receive the response after data trnascription has updated in every replica server believe
Breath, when the response message quantity received in the default renewal time is less than replica server total quantity, illustrates that existence is not updated successfully
Replica server, now, in the embodiment of the present invention, this replica server is not got rid of, but response message will not sent
Copy information corresponding to replica server be revised as continuing more new state, keep this replica server to continue to update.If in advance
If continuing in the renewal time, still do not receive the response message that the replica server continuing to update sends, then taken by this copy
The copy information that business device is corresponding is deleted from copy list, thus is got rid of from the data trnascription being updated successfully by this data trnascription.
The list attribute of copy list is changed owing to deleting copy information, the list attribute value of the embodiment of the present invention more latest copy list,
And the list attribute value after updating sends and is stored in central server.Compared with prior art, interior existence when updated
During the replica server not being updated successfully, it is not necessary to this replica server is got rid of, it is therefore not necessary to during current version number is stored in
In central server.And when getting rid of replica server, the change of copy list will necessarily be caused, therefore, the embodiment of the present invention is only
When copy list changes, list attribute value is stored central server such that it is able to reducing the shake of I/O performance
On the basis of, reduce the frequency writing data to central server, and then the pressure of central server can be reduced, improve system
Availability.
Corresponding with above-mentioned implementation method, the embodiment of the present invention additionally provides corresponding data update apparatus.Refer to figure
The structural representation of 4, Fig. 4 data update apparatus provided for the embodiment of the present invention.Described device includes: receiver module 11,
Status modifier module 12, removing module 13, more new module 14 and sending module 15, wherein, and described receiver module 11, use
In after the replica server transmission stored in copy list is more newly requested, receive data in every described replica server
Replica updating complete after response message;Described status modifier module 12, for when described receiver module 11 is default renewal
When the interior response message quantity received is less than the total quantity of described replica server, the Copy Service of response message will not sent
The copy information that device is corresponding is revised as continuing more new state;Described removing module 13, for presetting when described receiver module 12
When not receiving the response message that the described replica server continuing to update sends in continuing the renewal time yet, by described copy information
Delete from described copy list;Described more new module 14, for described removing module 13 by described copy information from described pair
After this list is deleted, update the list attribute value of described copy list;Described sending module 15, for by described more new module
The list attribute value that 14 are updated sends and is stored in central server.
In described device, the function of modules and the process that realizes of effect refer in said method corresponding to realize process,
This repeats no more.
By the present embodiment it can be seen that data update apparatus described in the embodiment of the present invention, when updated in exist not
During the replica server being updated successfully, it is not necessary to this replica server is got rid of, it is therefore not necessary to current version number is stored in center
In server.And when getting rid of replica server, the change of copy list will necessarily be caused, therefore, the embodiment of the present invention only exists
When copy list changes, list attribute value is stored central server such that it is able to reducing the shake of I/O performance
On the basis of, reduce the frequency writing data to central server, and then the pressure of central server can be reduced, improve system
Availability.
On the basis of above-described embodiment, described data update apparatus also includes generation module, described generation module, is used for
Generating that data are more newly requested and attribute is more newly requested, wherein, described attribute is more newly requested is the solicited message of more new version number;
In the present embodiment, described sending module 15, it is additionally operable to store in described copy list respectively the data trnascription clothes of data trnascription
It is more newly requested that business device sends described data;In described copy list, the attribute replica server of attribute information storage sends institute respectively
State attribute more newly requested.
On the basis of above-described embodiment, in the present embodiment, described generation module, specifically may be used for according to described sound
It is more newly requested that the version number answering copy corresponding to information generates attribute.Described sending module 15, is additionally operable to the described row after updating
Table Properties value sends respectively and stores in the replica server that described copy list is stored.
On the basis of above-described embodiment, described device also includes acquisition module and memory module, wherein, described acquisition mould
Block, for obtaining history list property value and history replica server address, wherein, described history from described central server
Replica server address is the replica server address of storage in the copy list that sent according to predetermined period;Described storage mould
Block, for when described pre-stored list property value is more than or equal to described history list property value, by described replica server
Corresponding address is stored in described copy list.In the present embodiment, described sending module 15, it is additionally operable to go through to described respectively
The replica server transmission Query Information that history replica server address is corresponding;Described receiver module 11, is additionally operable to receive described copy
Server responds the pre-stored list property value that described Query Information is sent.
In another embodiment, described device also includes determining module, described determines module, for by the highest for described version number
Data trnascription corresponding to copy information be defined as effective copy.In the present embodiment, described acquisition module, it is additionally operable to obtain often
Version number in copy information described in bar;Described removing module 13, is additionally operable to described version number less than described top version number
The copy information that copy information is corresponding is deleted from described copy list;Described more new module 14, is additionally operable to update described copy row
The list attribute of table is worth to new list attribute value;Described sending module 15, is additionally operable to update the list attribute of described copy list
It is worth to new list attribute value.
In described device, the function of modules and the process that realizes of effect refer in said method corresponding to realize process,
This repeats no more.
Seen from the above description, the data update apparatus that the embodiment of the present invention is provided, compared with prior art, when updated
During the replica server that interior existence is not updated successfully, it is not necessary to this replica server is got rid of, it is therefore not necessary to by current version number
It is stored in central server.And when getting rid of replica server, the change of copy list will necessarily be caused, and therefore, the present invention
List attribute value only when copy list changes, is stored central server by embodiment such that it is able to reducing I/O
The frequency writing data to central server can be reduced on the basis of shake, and then the pressure of central server can be reduced,
Improve system availability.
Corresponding with said method and device, the embodiment of the present invention additionally provides a kind of data update system, such as Fig. 5 institute
Show, the structural representation of the data update system that Fig. 5 provides for the embodiment of the present invention.Described system include client 1,
Replica server 2 and central server 3, wherein, client 1 includes above-mentioned data update apparatus, its function and work
Repeat no more by the embodiment of the present invention;Replica server 2, for receiving the list attribute value that described client 1 sends;
Central server 3, for receiving the list attribute value that described client 1 sends.
Seen from the above description, central server 3, being additionally operable to send acquisition copy information to described replica server 2 please
Ask, and receive the copy information that described replica server 2 sends, determine address list according to described copy information;By institute
List attribute value and the address list of storage are sent to described client 1;Replica server 2, is additionally operable to receive described center
The acquisition copy information request that server 3 sends, and described copy information is sent to described central server 3.Its tool
Body implementation method refers to foregoing description, and here is omitted for the embodiment of the present invention.
It is understood that the present invention can be used in numerous general or special purpose mobile terminal, such as: mobile phone, plate
Equipment computer etc..
To sum up, the problem low in order to solve system availability, data-updating method that the embodiment of the present invention is provided, device
And related system, the replica server stored in copy list respectively in client send more newly requested after, receive every pair
Response message after data trnascription has updated in book server, when the response message quantity received in the default renewal time is less than pair
During book server total quantity, illustrate to there is the replica server not being updated successfully, now, in the embodiment of the present invention, should not
Replica server is got rid of, but is revised as copy information corresponding for the replica server not sending response message continuing to update shape
State, keeps this replica server to continue to update.If within the default continuation renewal time, still do not receive the pair continuing to update
The response message that book server sends, then copy information corresponding for this replica server is deleted from copy list, thus will
This data trnascription is got rid of from the data trnascription being updated successfully.The list attribute of copy list is changed owing to deleting copy information,
The list attribute value of the embodiment of the present invention more latest copy list, and will update after list attribute value send and be stored in center service
In device.Compared with prior art, during the replica server that interior existence is not updated successfully when updated, it is not necessary to by this Copy Service
Device is got rid of, it is therefore not necessary to be stored in central server by current version number.And when getting rid of replica server, will necessarily make
Becoming the change of copy list, therefore, the embodiment of the present invention is only when copy list changes, in list attribute value being stored
Central server such that it is able on the basis of reducing the shake of I/O performance, reduce the frequency writing data to central server, enter
And the pressure of central server can be reduced, improve system availability.
The above is only the detailed description of the invention of the present invention, it is noted that for those skilled in the art
For, under the premise without departing from the principles of the invention, it is also possible to make some improvements and modifications, these improvements and modifications are also
Should be regarded as protection scope of the present invention.
Claims (14)
1. a data-updating method, it is characterised in that including:
After the replica server transmission stored in copy list is more newly requested, receive number in every described replica server
Response message after completing according to Replica updating;
When the response message quantity received in the default renewal time is less than the total quantity of described replica server, sound will not sent
The copy information answering the replica server of information corresponding is revised as continuing more new state;
When not receiving the response message that the described replica server continuing to update sends in the default continuation renewal time yet, by institute
State copy information to delete from described copy list;Update the list attribute value of described copy list, and the described row after updating
Table Properties value sends and is stored in central server.
2. the method for claim 1, it is characterised in that data trnascription updates in receiving every described replica server
Before response message after completing, also include:
Generate data more newly requested more newly requested with attribute;Wherein, described attribute is more newly requested is the solicited message of more new version number;
The described data of data trnascription server transmission storing data trnascription respectively in described copy list are more newly requested;Respectively to
In described copy list, the attribute replica server described attribute of transmission of attribute information storage is more newly requested.
3. the method for claim 1, it is characterised in that when the response message quantity received in the default renewal time is little
When the total quantity of described replica server, also include:
It is more newly requested that version number according to copy corresponding to described response message generates attribute;
It is separately sent to more newly requested for described attribute in attribute replica server.
4. the method for claim 1, it is characterised in that after updating the list attribute value of described copy list,
Before described list attribute value after updating sends and is stored in central server, also include:
Described list attribute value after updating sends respectively and stores in the replica server that described copy list is stored.
5. the method as described in claim arbitrary in Claims 1-4, it is characterised in that also include:
History list property value and history replica server address, wherein, described history copy is obtained from described central server
Server address is the replica server address of storage in the copy list that sent according to predetermined period;
Replica server corresponding to described history replica server address respectively sends Query Information;
Receive described replica server and respond the pre-stored list property value that described Query Information is sent;
When described pre-stored list property value is more than or equal to described history list property value, described replica server is corresponding
Address be stored in described copy list.
6. method as claimed in claim 5, it is characterised in that address corresponding for described replica server is being stored in institute
After stating in copy list, also include:
Obtain the version number in every described copy information;
Data trnascription corresponding for copy information the highest for described version number is defined as effective copy;
Copy information corresponding less than the copy information of described top version number for described version number is deleted from described copy list;
The list attribute updating described copy list is worth to new list attribute value;
Described new list attribute value is sent and is stored in described central server.
7. a data update apparatus, it is characterised in that including:
Receiver module, for the replica server that stored in copy list send more newly requested after, receive every described in
Response message after data trnascription has updated in replica server;
Status modifier module, is less than described for the response message quantity received within the default renewal time when described receiver module
During the total quantity of replica server, it is revised as copy information corresponding for the replica server not sending response message continuing to update shape
State;
Removing module, for not receiving the described copy continuing and updating yet when described receiver module within the default continuation renewal time
During the response message that server sends, described copy information is deleted from described copy list;
More new module, after described copy information is deleted from described copy list by described removing module, updates described copy
The list attribute value of list;
Sending module, for sending the list attribute value that described more new module is updated and be stored in central server.
8. device as claimed in claim 7, it is characterised in that also include: generation module, wherein,
Described generation module, is used for generating data more newly requested more newly requested with attribute;Wherein, described attribute is more newly requested is more
The solicited message of new version number;
Described sending module, the data trnascription server being additionally operable to store in described copy list respectively data trnascription sends described
Data are more newly requested;In described copy list, the attribute replica server transmission described attribute renewal of attribute information storage please respectively
Ask.
9. device as claimed in claim 7, it is characterised in that
Described generation module, the version number's generation attribute being additionally operable to the copy corresponding according to described response message is more newly requested.
10. device as claimed in claim 7, it is characterised in that
Described sending module, is additionally operable to the described list attribute value after updating and sends and store described copy list institute respectively
In the replica server of storage.
Device as described in arbitrary claim in 11. such as claim 7 to 10, it is characterised in that also include: acquisition module and storage
Module, wherein,
Described acquisition module, for obtaining history list property value and history replica server address from described central server,
Wherein, the replica server ground that described history replica server address is storage in the copy list that sent according to predetermined period
Location;
Described sending module, is additionally operable to replica server corresponding to described history replica server address respectively and sends inquiry letter
Breath;
Described receiver module, is additionally operable to receive described replica server and responds the pre-stored list attribute that described Query Information is sent
Value;
Described memory module, is used for when described pre-stored list property value is more than or equal to described history list property value, will
The address that described replica server is corresponding is stored in described copy list.
12. devices as claimed in claim 11, it is characterised in that also include determining module, wherein,
Described acquisition module, is additionally operable to obtain the version number in every described copy information;
Described determine module, for data trnascription corresponding for copy information the highest for described version number is defined as effective copy;
Described removing module, be additionally operable to by copy information corresponding less than the copy information of described top version number for described version number from
Described copy list is deleted;
Described more new module, the list attribute being additionally operable to update described copy list is worth to new list attribute value;
Described sending module, the list attribute being additionally operable to update described copy list is worth to new list attribute value.
13. 1 kinds of data update systems, it is characterised in that include client, replica server and central server, wherein,
Described client is as described in claim arbitrary in claim 7 to 12;
Described replica server, for receiving the list attribute value that described client sends;
Described central server, for receiving the list attribute value that described client sends.
14. devices as claimed in claim 13, it is characterised in that
Described central server, is additionally operable to send to described replica server obtain copy information request, and receives described pair
The copy information that book server sends, determines address list according to described copy information;By the list attribute value stored and
Address list is sent to described client;
Described replica server, is additionally operable to receive the acquisition copy information request that described central server sends, and by described
Copy information is sent to described central server.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510363437.6A CN106302625B (en) | 2015-06-26 | 2015-06-26 | Data-updating method, device and related system |
PCT/CN2016/086106 WO2016206568A1 (en) | 2015-06-26 | 2016-06-17 | Data update method, device, and related system |
US15/852,653 US20180121531A1 (en) | 2015-06-26 | 2017-12-22 | Data Updating Method, Device, and Related System |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510363437.6A CN106302625B (en) | 2015-06-26 | 2015-06-26 | Data-updating method, device and related system |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106302625A true CN106302625A (en) | 2017-01-04 |
CN106302625B CN106302625B (en) | 2019-10-25 |
Family
ID=57584700
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201510363437.6A Active CN106302625B (en) | 2015-06-26 | 2015-06-26 | Data-updating method, device and related system |
Country Status (3)
Country | Link |
---|---|
US (1) | US20180121531A1 (en) |
CN (1) | CN106302625B (en) |
WO (1) | WO2016206568A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107770281A (en) * | 2017-11-01 | 2018-03-06 | 深圳市金立通信设备有限公司 | A kind of method, server and computer-readable recording medium for notifying trade company's reimbursement information |
CN110377381A (en) * | 2019-06-27 | 2019-10-25 | 苏州浪潮智能科技有限公司 | A kind of the list method for refreshing and device of information system |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11221785B2 (en) * | 2019-12-03 | 2022-01-11 | Western Digital Technologies, Inc. | Managing replication state for deleted objects |
CN115987759B (en) * | 2023-02-17 | 2023-06-23 | 天翼云科技有限公司 | Data processing method, device, electronic equipment and storage medium |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5434994A (en) * | 1994-05-23 | 1995-07-18 | International Business Machines Corporation | System and method for maintaining replicated data coherency in a data processing system |
CN101741911A (en) * | 2009-12-18 | 2010-06-16 | 中兴通讯股份有限公司 | Multi-copy collaboration-based write operation method, system and node |
US20100199042A1 (en) * | 2009-01-30 | 2010-08-05 | Twinstrata, Inc | System and method for secure and reliable multi-cloud data replication |
CN101853269A (en) * | 2010-04-29 | 2010-10-06 | 中国人民解放军国防科学技术大学 | Consistent processing method for updating distributed data |
CN101964820A (en) * | 2010-10-08 | 2011-02-02 | 中兴通讯股份有限公司 | Method and system for keeping data consistency |
CN103036717A (en) * | 2012-12-12 | 2013-04-10 | 北京邮电大学 | Consistency maintenance system and methods for distributed-type data |
CN103294675A (en) * | 2012-02-23 | 2013-09-11 | 上海盛霄云计算技术有限公司 | Method and device for updating data in distributed storage system |
CN103729352A (en) * | 2012-10-10 | 2014-04-16 | 腾讯科技(深圳)有限公司 | Distributed file system and method for processing multiple replica data in distributed file system |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4173673B2 (en) * | 2002-03-20 | 2008-10-29 | 株式会社日立製作所 | File backup method and storage device |
US7433928B1 (en) * | 2003-12-31 | 2008-10-07 | Symantec Operating Corporation | System pre-allocating data object replicas for a distributed file sharing system |
US7734820B1 (en) * | 2003-12-31 | 2010-06-08 | Symantec Operating Corporation | Adaptive caching for a distributed file sharing system |
CN102833273B (en) * | 2011-06-13 | 2017-11-03 | 中兴通讯股份有限公司 | Data recovery method and distributed cache system during temporary derangement |
CN103327116B (en) * | 2013-07-05 | 2016-06-01 | 山东大学 | The dynamic copies storage means of a kind of network file |
CN104239182B (en) * | 2014-09-03 | 2017-05-03 | 北京鲸鲨软件科技有限公司 | Cluster file system split-brain processing method and device |
-
2015
- 2015-06-26 CN CN201510363437.6A patent/CN106302625B/en active Active
-
2016
- 2016-06-17 WO PCT/CN2016/086106 patent/WO2016206568A1/en active Application Filing
-
2017
- 2017-12-22 US US15/852,653 patent/US20180121531A1/en not_active Abandoned
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5434994A (en) * | 1994-05-23 | 1995-07-18 | International Business Machines Corporation | System and method for maintaining replicated data coherency in a data processing system |
US20100199042A1 (en) * | 2009-01-30 | 2010-08-05 | Twinstrata, Inc | System and method for secure and reliable multi-cloud data replication |
CN101741911A (en) * | 2009-12-18 | 2010-06-16 | 中兴通讯股份有限公司 | Multi-copy collaboration-based write operation method, system and node |
CN101853269A (en) * | 2010-04-29 | 2010-10-06 | 中国人民解放军国防科学技术大学 | Consistent processing method for updating distributed data |
CN101964820A (en) * | 2010-10-08 | 2011-02-02 | 中兴通讯股份有限公司 | Method and system for keeping data consistency |
CN103294675A (en) * | 2012-02-23 | 2013-09-11 | 上海盛霄云计算技术有限公司 | Method and device for updating data in distributed storage system |
CN103729352A (en) * | 2012-10-10 | 2014-04-16 | 腾讯科技(深圳)有限公司 | Distributed file system and method for processing multiple replica data in distributed file system |
CN103036717A (en) * | 2012-12-12 | 2013-04-10 | 北京邮电大学 | Consistency maintenance system and methods for distributed-type data |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107770281A (en) * | 2017-11-01 | 2018-03-06 | 深圳市金立通信设备有限公司 | A kind of method, server and computer-readable recording medium for notifying trade company's reimbursement information |
CN110377381A (en) * | 2019-06-27 | 2019-10-25 | 苏州浪潮智能科技有限公司 | A kind of the list method for refreshing and device of information system |
Also Published As
Publication number | Publication date |
---|---|
CN106302625B (en) | 2019-10-25 |
US20180121531A1 (en) | 2018-05-03 |
WO2016206568A1 (en) | 2016-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11586673B2 (en) | Data writing and reading method and apparatus, and cloud storage system | |
CN111091429B (en) | Electronic bill identification distribution method and device and electronic bill generation system | |
CN108228814B (en) | Data synchronization method and device | |
CN103294675B (en) | Data-updating method and device in a kind of distributed memory system | |
CN103473277B (en) | The Snapshot Method and device of file system | |
CN111045985B (en) | File storage processing method, server, electronic device and storage medium | |
CN106302625A (en) | Data-updating method, device and related system | |
CN106708653B (en) | Mixed tax big data security protection method based on erasure code and multiple copies | |
CN103152390A (en) | Method and device and nodes and system for node configuration of distributed storage system | |
CN104202423A (en) | System for extending caches by aid of software architectures | |
CN102902561A (en) | Data storage method and data storage system | |
CN109491832A (en) | Data disaster tolerance method and website | |
CN111241108A (en) | Key value pair-based KV system indexing method and device, electronic equipment and medium | |
CN115934414A (en) | Data backup method, data recovery method, device, equipment and storage medium | |
CN107203437A (en) | The methods, devices and systems for preventing internal storage data from losing | |
CN102609454A (en) | Replica management method for distributed file system | |
CN104391760A (en) | Data backup method, server and system | |
CN111984198A (en) | Message queue implementation method and device and electronic equipment | |
CN109542841B (en) | Method for creating data snapshot in cluster and terminal equipment | |
CN111581017A (en) | Backup and recovery system and method for modern application | |
CN107357808B (en) | Data management method, device and equipment | |
CN111767284B (en) | Data processing method, device, storage medium and server | |
CN112437125B (en) | Information concurrent processing method and device, electronic equipment and storage medium | |
CN105550347B (en) | Data processing method and device | |
CN108460078B (en) | Auxiliary function execution method and device, storage medium and terminal |
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 |