CN107545060A - A kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata - Google Patents
A kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata Download PDFInfo
- Publication number
- CN107545060A CN107545060A CN201710769240.1A CN201710769240A CN107545060A CN 107545060 A CN107545060 A CN 107545060A CN 201710769240 A CN201710769240 A CN 201710769240A CN 107545060 A CN107545060 A CN 107545060A
- Authority
- CN
- China
- Prior art keywords
- redis
- file synchronization
- synchrodata
- data
- synchronization event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Computer And Data Communications (AREA)
Abstract
The present invention provides a kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata, redis host nodes are when the timed events set with preset time period start, the file synchronization event created before the timed events start is performed, the file synchronization event is used to control the redis host nodes to send rdb files to the redis from node；According to the transmission rate of the file synchronization event qualification, the synchrodata in the rdb files is sent；The synchrodata is sent in the preset time period and deletes the file synchronization event.Therefore the present invention can control the speed of master-slave synchronisation, ensure that master-slave synchronisation will not take whole bandwidth of network interface card, so as to ensure that business normal operation.
Description
Technical field
The present invention relates to data synchronization technology field, more particularly to a kind of speed limit side of redis principals and subordinates full dose synchrodata
Method and device.
Background technology
Redis is a high performance database increased income, and has very high readwrite performance, can will be stored in internal memory
Key-value pair data is persisted to hard disk, and user can configure different persistence modes according to actual use scene.In order to carry
The high stability of a system, the host-guest architecture of redis system generally uses.In redis from the initial phase of node, it is necessary to will
Data full dose on redis host nodes replicates portion, to make principal and subordinate's full dose synchronization that this standby event is referred to as redis.
In principal and subordinate's full dose synchronizing process, redis host nodes are led to using TCP when sending rdb files from node to redis
Letter, i.e. redis host nodes send 16k (byte) data to redis from node every time, have sent and have and then sent next time
16k data, are ceaselessly cycled through always, untill the data in rdb files have been sent.Due to such redis host nodes
Continue ceaselessly to send data to redis from node, sharply increase the data transfer bandwidth between main and subordinate node, even up to
The bandwidth bottleneck of network interface card, when network interface card bandwidth is fully occupied, between main and subordinate node then can not proper communication, so as to cause
The service exception of redis systems.
The content of the invention
In view of this, a kind of method for limiting speed of redis principals and subordinates full dose synchrodata of present invention offer and device are complete to solve
Amount synchronously causes bandwidth the problem of bottleneck occur.
Specifically, the present invention is achieved through the following technical solutions：
On the one hand, the present invention provides a kind of method for limiting speed of redis principals and subordinates full dose synchrodata, and methods described is applied to
Redis host nodes in redis systems, methods described include：
When the timed events set with preset time period start, the text created before the timed events start is performed
Part synchronous event, the file synchronization event are used to control the redis host nodes to send rdb texts to the redis from node
Part；
According to the transmission rate of the file synchronization event qualification, the synchrodata in the rdb files is sent；
The synchrodata is sent in the preset time period and deletes the file synchronization event.
On the other hand, conceived based on identical, the present invention also provides a kind of speed limit dress of redis principals and subordinates full dose synchrodata
Put, described device is applied to the redis host nodes in redis systems, and described device includes：
Event creating unit, during for starting in the timed events set with preset time period, perform in the timing thing
Part starts the file synchronization event created before, and the file synchronization event is used to controlling the redis host nodes to described
Redis sends rdb files from node；
Data transmission unit, for the transmission rate according to the file synchronization event qualification, send in the rdb files
Synchrodata；
Event deletes unit, for sending the synchrodata in the preset time period and deleting the file synchronization
Event.
The beneficial effect that technical scheme provided in an embodiment of the present invention is brought is：
The present invention makes redis host nodes be performed when the timed events set with preset time period start in the timing
Event starts the file synchronization event created before, for controlling the redis host nodes to be sent to the redis from node
Rdb files；Then redis host nodes can be sent in the rdb files according to the transmission rate of the file synchronization event qualification
Synchrodata, and send in the preset time period synchrodata and delete the file synchronization event.Compared to
Prior art, the present invention can according to the speed of restriction in preset time period synchrodata, and deleted in preset time period
Except file synchronization event, so as to adjust the data of master-slave synchronisation in each timed events according to speed limit, ensure that master-slave synchronisation will not
Whole bandwidth of network interface card are taken, so as to ensure that business normal operation.
Brief description of the drawings
Technical scheme in order to illustrate the embodiments of the present invention more clearly, make required in being described below to embodiment
Accompanying drawing is briefly described, it should be apparent that, drawings in the following description are only some embodiments of the present invention, for
For those of ordinary skill in the art, on the premise of not paying creative work, other can also be obtained according to these accompanying drawings
Accompanying drawing.
Fig. 1 is a kind of method for limiting speed of redis principals and subordinates full dose synchrodata in a kind of illustrative embodiments of the present invention
Process chart；
Fig. 2 is the relation schematic diagram of time span in a kind of illustrative embodiments of the present invention；
Fig. 3 is the speed limit side of another redis principals and subordinates full dose synchrodata in a kind of illustrative embodiments of the present invention
The process chart of method；
Fig. 4 is the speed-limiting device place of redis principal and subordinate's full dose synchrodatas in a kind of illustrative embodiments of the present invention
The hardware structure diagram of equipment；
Fig. 5 is a kind of speed-limiting device of redis principals and subordinates full dose synchrodata in a kind of illustrative embodiments of the present invention
Building-block of logic.
Embodiment
To make the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing to embodiment party of the present invention
Formula is described in further detail.
Fig. 1 is refer to, is a kind of limit of redis principals and subordinates full dose synchrodata in a kind of illustrative embodiments of the present invention
The process chart of fast method, methods described are applied to the redis host nodes in redis systems, and methods described includes：
Step 101, when the timed events set with preset time period start, perform before the timed events start
The file synchronization event of establishment, the file synchronization event are used to control the redis host nodes to send out to the redis from node
Send rdb files；
In the present embodiment, timed events and file synchronization thing are generally included in redis principal and subordinate's full dose synchronizing process
Part；Wherein timed events refer in redis principal and subordinate's full dose synchronizing process, and the timing set with preset time period triggers
Timed events, it is understood that the event triggered for current time period and the critical moment of next time cycle.
As one embodiment, redis host nodes can use to be touched in a manner of preset time period sets timing to stab
Timed events are sent out, i.e., when redis host nodes judge now to reach timing stamp, it is believed that new timed events are opened,
Then next timing is set to stab further according to timed interval in new timed events, so as to when arriving next timing
Between stab when open next timed events.For example, the timing stamp of starting is t=0ms, when reaching 0ms, then first is opened
Individual timed events；Assuming that current preset time period is 100ms, then it is in t=100ms to set next timing；And
When the time reaching 100ms, next timed events are opened, by that analogy.
In the present embodiment, when each timed events start, redis host nodes can perform to be opened in the timed events
Begin the file synchronization event that creates before, the file synchronization event be used to controlling the redis host nodes to the redis from
Node sends rdb files.
Create and perform file synchronization event, the file synchronization event is specially redis host nodes according to location tags
Rdb files are sent to redis from node, the location tags refer to the original position of data to be synchronized in rdb files, position mark
Label can change according to the change of the cumulative data amount sent.
As one embodiment, when each timed events start, redis host nodes can also first judge whether to need together
Rdb files of step, such as at the end of having new rdb processes, or rdb files before without it is synchronous complete when, illustrate now
Need to carry out rdb file synchronizations, therefore can be with establishment file synchronous event.
Step 102, the transmission rate according to the file synchronization event qualification, send the same step number in the rdb files
According to；
In the present embodiment, redis host nodes can send institute according to the transmission rate of the file synchronization event qualification
State the synchrodata in rdb files.For example, the server on general line be 1000Mbps network interface card, then principal and subordinate is same
The peak data transfer rate of step is 1000/8=125M k/s (as shown in the time shaft on the upside of Fig. 2), it is contemplated that 1000Mbps's
Network interface card will be made when network interface card, the data transmission rate 900Mbps between principal and subordinate or so, therefore in order to avoid network interface card bandwidth
It is fully occupied, increases a speed limit strategy in master-slave synchronisation, i.e., by master-slave synchronisation rate limitation in 100M k/s (such as Fig. 2
Shown in the time shaft of downside), so as to the velocity magnitude 100M k/s according to limitation, guarantee is per second to send preset data to from node
Amount is 100M, i.e., average per 100ms synchronization 10M data.Compared to prior art not speed limit when averagely per 100ms synchronizations 12.5M
Data, the present invention do not continue to send by speed limit, control averagely per 100ms synchronization 10M data, and after being sent completely, until
10M data are retransmited during next 100ms, so as to which network interface card flow can be controlled, avoid a network interface card bandwidth from making.Therefore explanation
The present invention can control the data volume in the rdb files sent in each timed events after speed limit, make in timed events
The synchrodata amount of transmission is less than the data volume of bandwidth limitation.
Step 103, the synchrodata and the deletion file synchronization event are sent in the preset time period.
In the present embodiment, redis host nodes can send the synchrodata in the preset time period, then delete
Except the file synchronization event.Specifically, redis host nodes can be recorded according to the transmission rate and pre- less than described
If the data volume for the synchrodata that the target time section of period determines.For example, because master-slave synchronisation rate limitation is in 100M k/
S (as shown in the time shaft on the downside of Fig. 2), preset time period are 100ms, are cycled through due to just being controlled when timed events start
10M data so that the 10M data are sent completely in 80ms, synchrodata are not sent in remaining 20ms, therefore the 80ms is
Target time section, it can be when timed events start, transmission rate is lifted to 125M k/s from 100M k/, or fixed
When event target time section is set when starting to send the time of synchrodata, so as to according to the transmission speed size in 80ms
125M k/s, ensure the data volume i.e. 125M k/s*80ms for the synchrodata that each target time section is sent to redis from node
=10M data.
As one embodiment, the synchronous rdb files of redis host nodes are the temporary files in disk, including rising
Beginning location tags, for indicating the original position of reading file.When file synchronization event starts, it is necessary to rdb files in disk
Original position label start to read the data volume equal with sending threshold value file synchronization carried out into caching.
When the data volume of synchrodata is equal with the sending threshold value that the file synchronization event is set in timed events, table
Show that the synchronous data volume of this needs has reached, therefore no longer synchrodata, redis host nodes are big according to the data volume
It is used to indicate the original position label for sending the data volume in the small adjustment rdb.Due to the data volume and hair of synchrodata
Send threshold value equal, therefore the original position label of the rdb files in disk can be moved rearwards synchrodata by redis host nodes
Data volume size distance, so as to control redis host nodes in each timed events only send be less than or equal to hair
Send the file data amount of threshold value.
As one embodiment, specific synchronous method is：Redis host nodes are with the fixed data less than the data volume
Amount cycles through the data volume, and cumulative calculation is carried out to the fixed data amount and obtains accumulative traffic volume.
When the accumulative traffic volume is equal to the sending threshold value, and cycle through the duration section of the fixed traffic volume
During no more than the target time section, redis host nodes can consider that the estimated file data sent is in current timed events
Through completing, therefore it can stop cycling through the first process of the fixed traffic volume, first process stops representing to send
The data volume is completed；And when first process stops, redis host nodes can delete the file synchronization event.Together
When, because accumulative traffic volume is equal to sending threshold value, therefore redis host nodes can also be in the original position mark in the rdb files
The Data Position that the sending threshold value is spaced after label adds label for updating the original position.
When the accumulative traffic volume is less than the sending threshold value, and cycle through the duration section of the fixed traffic volume
During equal to the target time section, redis host nodes can consider that the file data of estimated transmission in current timed events is not complete
Into, but in order to not cause bandwidth burden, redis host nodes can stop cycling through in the finish time of the target time section
Second process of the fixed traffic volume, and when second process stops, deleting the file synchronization event.Meanwhile by
It is less than sending threshold value in accumulative traffic volume, therefore is spaced after original position label of the redis host nodes in the rdb files
The Data Position of the cumulative data amount adds the label for updating the original position.
For example, it is each using TCP communication, i.e. redis host nodes when redis host nodes perform file synchronization event
The data that fixed data amount is 16k are sent to redis from node, it is assumed that object time 80ms, the data volume of synchrodata are
10M, redis host node fixed data amount 16k cycle through the data volume 10M, and the fixed data amount 16k is carried out
Cumulative calculation obtains accumulative traffic volume, such as the first time after transmission 16k data, it is then 16k to add up traffic volume, is sent out again for the second time
After sending 16k data, it is then 16k+16k=32k to add up traffic volume, by that analogy.
When redis host nodes are within the time less than 80ms, the accumulative traffic volume for judging to send is equal to sending threshold value 10M
When, then it is assumed that the estimated file data sent has been completed in current timed events, therefore stops cycling through the fixed hair
First process of the amount of sending；And delete the file synchronization event.Meanwhile redis host nodes can also be in the rdb files rise
The Data Position that the sending threshold value 10M is spaced after beginning location tags adds label for updating the original position, then
10M data are still read from disk next time into caching.
When redis host nodes reach 80ms, the accumulative traffic volume of transmission is assumed to be 8M, less than sending threshold value 10M, then
Think that the file data of estimated transmission in current timed events there remains 2M and not complete, redis host nodes can be in the target
Between finish time (during 80ms) of section stop cycling through the second process of the fixed traffic volume, and delete the file synchronization
Event.Meanwhile therefore original position label of the redis host nodes in the rdb files after be spaced the cumulative data amount
8M Data Position adds the label for updating the original position, then only reads 8M data next time into caching.
Ground can be revolved, original position label is deleted after the label for being used for updating original position is added, is now used to update
The tag update of original position is original position label；The label and start bit for updating original position can also be used for according to addition
The time sequencing of label is put, to aforementioned label successively label, when reading 8M data, then rising for 8M data is searched according to maximum label
Beginning position.
In an alternate embodiment of the invention, when file synchronization event is deleted, if current rdb files do not synchronously complete,
The original position label in rdb files is deleted, if current rdb files are all sent completely, illustrates redis principal and subordinate's full dose
Synchronizing process has been completed, and subsequently without file synchronization, therefore can delete rdb temporary files and original position label.
As one embodiment, before timed events are created, it can also further detect and be used on the redis host nodes
In the open command limited the transmission rate, if detecting the open command, illustrate that this redis principal and subordinate is complete
Amount synchronously needs to carry out speed limit, so as to create the timed events, according to above-mentioned redis principal and subordinate's full dose synchrodata
It is synchronous that method for limiting speed carries out principal and subordinate's full dose；If not detecting the open command, illustrate that this redis principal and subordinate is complete
Amount does not need speed limit synchronously, therefore it is synchronous to carry out principal and subordinate's full dose according to existing method.Therefore the present invention can with it is existing
Principal and subordinate's full dose method of synchronization between free switching, the flexibility of lifting system.
For the objects, technical solutions and advantages of the present invention are more clearly understood, with reference to Fig. 3 to the solution of the present invention
It is described in further detail.
Refer to Fig. 3 is another redis principals and subordinates full dose synchrodata in a kind of illustrative embodiments of the present invention
The process chart of method for limiting speed, this method are applied to the redis host nodes in redis systems, and the redis host nodes can week
Flow shown in execution Fig. 3 of phase property, methods described include；
When step 301, timed events start, file synchronization event is performed, goes to step 302；
In the present embodiment, redis host nodes can perform timed events, such as timing according to timed interval
During at intervals of 100ms, redis host nodes start to perform a timed events per 100ms.Before timed events, first determine whether
Current redis host nodes synchronous rdb files whether in need, if so, then establishment file synchronous event, this document synchronization thing
Accumulative traffic volume and original position label are carried in part.If before local have recorded accumulative traffic volume and original position mark
Label, then using the information of local record, if local do not record, when illustrating currently to have new rdb file needs synchronous, then
The accumulative traffic volume sent is 0k, and original position label is 0k.
Step 302, the data for sending fixed data amount, go to step 303；
Principal and subordinate's file synchronization of the present invention can use TCP communication, and sending fixed data amount from node to redis every time is
16k data；
The accumulative traffic volume of step 303, record, goes to step 304；
After redis host nodes have sent 16k data, accumulative traffic volume is recorded.For example, if accumulative traffic volume before is
0k, then the accumulative traffic volume after updating is 16k；If accumulative traffic volume before is 100k, the accumulative traffic volume after renewal
For 116k.
Step 304, judge whether accumulative traffic volume is equal to sending threshold value in target time section, if so, then going to step
305；If it is not, then go to step 306；
In the present embodiment, sending threshold value is according to current limliting policy development, by taking 1000Mbps network interface card as an example, master-slave synchronisation
Peak data transfer rate be 1000/8=125M k/s, when using current limliting strategy when, by master-slave synchronisation rate limitation in 100M
K/s, i.e., average that 10M data are sent per 100ms, i.e. sending threshold value is 10M, it is assumed that target time section 80ms, therefore redis master
Node further determines whether to be sent completely 10M data according to accumulative traffic volume.
Step 305, file synchronization event is deleted, original position label is updated according to sending threshold value, and terminate；
If being sent completely the data volume of sending threshold value, file synchronization event can be deleted, according to sending threshold value 10M more
New original position label, example original position label as in the previous is 1000k, then the original position label after updating is 2000K,
So that subsequent file synchronous event is sent since 2000k data.
Step 306, file synchronization event is deleted, original position label is updated according to accumulative traffic volume, and terminate.
If not being sent completely the data volume of sending threshold value, such as 8M data are only have sent, then can delete file synchronization
Event, original position label is updated according to accumulative traffic volume 8M, example original position label as in the previous is 1000k, then after updating
Original position label be 1800K so that subsequent file synchronous event is sent since 1800k data.
Compared to prior art, the present invention can control the data volume of synchrodata according to speed limit, according to being actually needed
Dynamic adjusts the speed of master-slave synchronisation, ensures that master-slave synchronisation will not take whole bandwidth of network interface card, so as to ensure that business is normal
Operation.In practical application, user can also adjust the size of speed limit according to practical business pressure condition on line, so as to ensure
While business processing speed, avoid taking network interface card bandwidth, so as to improve the stability of redis systems.
Conceived based on identical, the present invention also provides a kind of speed-limiting device of redis principals and subordinates full dose synchrodata, the device
It can be realized, can also be realized by way of hardware or software and hardware combining by software.Exemplified by implemented in software, the present invention
Redis principal and subordinate's full dose synchrodatas speed-limiting device as the device on a logical meaning, be by redis master where it
The CPU of node device runs after corresponding computer program instructions in memory are read and formed.
Fig. 4 is refer to, is a kind of limit of redis principals and subordinates full dose synchrodata in a kind of illustrative embodiments of the present invention
Speed variator 500, described device are applied to the redis host nodes in redis systems, and the basic running environment of the device includes CPU, deposited
Reservoir and other hardware, from logic level, the logical construction of the device 500 as shown in figure 5, including：
Event creating unit 501, during for starting in the timed events set with preset time period, perform in the timing
Event starts the file synchronization event created before, and the file synchronization event is used to controlling the redis host nodes to described
Redis sends rdb files from node；
Data transmission unit 502, for the transmission rate according to the file synchronization event qualification, send the rdb texts
Synchrodata in part；
Event deletes unit 503, for sending the synchrodata in the preset time period and deleting the file
Synchronous event.
Optionally, the event deletes unit 503, with the transmission rate and pre- less than described specifically for recording
If the data volume for the synchrodata that the target time section of period determines；When the data volume and the file synchronization event
When the sending threshold value of setting is equal, is adjusted according to the size of the data volume and be used to indicate to send the data volume in the rdb
Original position label.
The function of unit and the implementation process of effect specifically refer to and step are corresponded in the above method in said apparatus
Implementation process, it will not be repeated here.
In summary, the present invention makes redis host nodes be performed when the timed events set with preset time period start
The timed events start the file synchronization event created before, for controlling the redis host nodes to the redis from section
Point sends rdb files；Then redis host nodes can send the rdb according to the transmission rate of the file synchronization event qualification
Synchrodata in file, and the synchrodata and the deletion file synchronization event are sent in the preset time period.
Compared to prior art, the present invention can according to the speed of restriction in preset time period synchrodata, and in preset time
File synchronization event is deleted in section, so as to adjust the data of master-slave synchronisation in each timed events according to speed limit, ensures that principal and subordinate is same
Step will not take whole bandwidth of network interface card, so as to ensure that business normal operation.
For device embodiment, because it corresponds essentially to embodiment of the method, so related part is real referring to method
Apply the part explanation of example.Device embodiment described above is only schematical, wherein described be used as separating component
The unit of explanation can be or may not be physically separate, can be as the part that unit is shown or can also
It is not physical location, you can with positioned at a place, or can also be distributed on multiple NEs.Can be according to reality
Need to select some or all of module therein to realize the purpose of application scheme.Those of ordinary skill in the art are not paying
In the case of going out creative work, you can to understand and implement.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all essences in the present invention
God any modification, equivalent substitution and improvements done etc., should be included within the scope of protection of the invention with principle.
Claims (10)
1. a kind of method for limiting speed of redis principals and subordinates full dose synchrodata, it is characterised in that methods described is applied to redis systems
In redis host nodes, methods described includes：
When the timed events set with preset time period start, it is same to perform the file created before the timed events start
Step event, the file synchronization event are used to control the redis host nodes to send rdb files to the redis from node；
According to the transmission rate of the file synchronization event qualification, the synchrodata in the rdb files is sent；
The synchrodata is sent in the preset time period and deletes the file synchronization event.
2. according to the method for claim 1, it is characterised in that sent in the preset time period synchrodata and
The file synchronization event is deleted, is specifically also included：
The number for the synchrodata that record determines with the transmission rate and less than the target time section of the preset time period
According to amount；
When the data volume is equal with the sending threshold value that the file synchronization event is set, according to the big ditty of the data volume
It is used to indicate the original position label for sending the data volume in the whole rdb.
3. according to the method for claim 2, it is characterised in that sent in the preset time period synchrodata and
The file synchronization event is deleted, methods described also includes：
The data volume is cycled through and for the fixed data amount cumulative calculation with the fixed data amount less than the data volume
Obtain accumulative traffic volume；
When the accumulative traffic volume is equal to the sending threshold value, and cycle through the duration Duan Buchao of the fixed traffic volume
When crossing the target time section, stop cycling through the first process of the fixed traffic volume, first process stops representing
The data volume is sent to complete；
When first process stops, the file synchronization event is deleted.
4. according to the method for claim 3, it is characterised in that described that the rdb is adjusted according to the size of the data volume
In be used to indicate the original position label for sending the data volume, be specially：
The Data Position that the sending threshold value is spaced after original position label in the rdb files is added for updating institute
The label of original position is stated, and the original position label is deleted after adding the label for updating the original position.
5. according to the method for claim 3, it is characterised in that sent in the preset time period synchrodata and
The file synchronization event is deleted, methods described also includes：
When the accumulative traffic volume is less than the sending threshold value, and the duration section for cycling through the fixed traffic volume is equal to
During the target time section, cycle through the second of the fixed traffic volume in the finish time stopping of the target time section and enter
Journey；
When second process stops, the file synchronization event is deleted.
6. according to the method for claim 5, it is characterised in that described that the rdb is adjusted according to the size of the data volume
In be used to indicate the original position label for sending the data volume, be specially：
The Data Position that the cumulative data amount is spaced after original position label in the rdb files is added for updating
The label of the original position.
7. according to the method described in claim 1-6, it is characterised in that start in the timed events set with preset time period
When, the file synchronization event created before the timed events start is performed, is specifically also included：
Detect the open command for being used to limit the transmission rate on the redis host nodes；
When detecting the open command, the timed events are created.
8. according to the method described in claim 1-6, it is characterised in that when the timed events start, in addition to：
When the timed events start, the rdb files to be synchronized are determined whether, if so, it is same then to create the file
Step event.
9. a kind of speed-limiting device of redis principals and subordinates full dose synchrodata, it is characterised in that described device is applied to redis systems
In redis host nodes, described device includes：
Event creating unit, during for starting in the timed events set with preset time period, performing and being opened in the timed events
Begin the file synchronization event that creates before, the file synchronization event be used to controlling the redis host nodes to the redis from
Node sends rdb files；
Data transmission unit, for the transmission rate according to the file synchronization event qualification, send same in the rdb files
Step data；
Event deletes unit, for sending the synchrodata in the preset time period and deleting the file synchronization thing
Part.
10. device according to claim 9, it is characterised in that
The event deletes unit, specifically for recording with the transmission rate and the object time less than the preset time period
The data volume for the synchrodata that section determines；When the data volume is equal with the sending threshold value that the file synchronization event is set
When, adjusted according to the size of the data volume and be used to indicate the original position label for sending the data volume in the rdb.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710769240.1A CN107545060A (en) | 2017-08-31 | 2017-08-31 | A kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710769240.1A CN107545060A (en) | 2017-08-31 | 2017-08-31 | A kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107545060A true CN107545060A (en) | 2018-01-05 |
Family
ID=60957930
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710769240.1A Pending CN107545060A (en) | 2017-08-31 | 2017-08-31 | A kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107545060A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110134454A (en) * | 2018-02-09 | 2019-08-16 | 聚好看科技股份有限公司 | A kind of method and device thereof starting application program |
| CN111680100A (en) * | 2020-04-30 | 2020-09-18 | 聚好看科技股份有限公司 | Redis data synchronization method and server |
| CN112653734A (en) * | 2020-12-11 | 2021-04-13 | 邦彦技术股份有限公司 | Server cluster real-time master-slave control and data synchronization system and method |
| CN112860794A (en) * | 2021-02-03 | 2021-05-28 | 百果园技术(新加坡)有限公司 | Cache-based concurrency capability improving method, device, equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105528366A (en) * | 2014-09-30 | 2016-04-27 | 阿里巴巴集团控股有限公司 | A data synchronization control method and device |
| CN106469158A (en) * | 2015-08-17 | 2017-03-01 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| CN106603640A (en) * | 2016-12-05 | 2017-04-26 | 北京中交兴路信息科技有限公司 | Data synchronizing method and device |
| US20170124695A1 (en) * | 2015-10-29 | 2017-05-04 | Samsung Electronics Co., Ltd. | Data processing apparatus |
| CN106657169A (en) * | 2015-10-28 | 2017-05-10 | 北京京东尚科信息技术有限公司 | Main and slave node data synchronization method in Redis |
-
2017
- 2017-08-31 CN CN201710769240.1A patent/CN107545060A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105528366A (en) * | 2014-09-30 | 2016-04-27 | 阿里巴巴集团控股有限公司 | A data synchronization control method and device |
| CN106469158A (en) * | 2015-08-17 | 2017-03-01 | 杭州海康威视系统技术有限公司 | Method of data synchronization and device |
| CN106657169A (en) * | 2015-10-28 | 2017-05-10 | 北京京东尚科信息技术有限公司 | Main and slave node data synchronization method in Redis |
| US20170124695A1 (en) * | 2015-10-29 | 2017-05-04 | Samsung Electronics Co., Ltd. | Data processing apparatus |
| CN106603640A (en) * | 2016-12-05 | 2017-04-26 | 北京中交兴路信息科技有限公司 | Data synchronizing method and device |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110134454A (en) * | 2018-02-09 | 2019-08-16 | 聚好看科技股份有限公司 | A kind of method and device thereof starting application program |
| CN111680100A (en) * | 2020-04-30 | 2020-09-18 | 聚好看科技股份有限公司 | Redis data synchronization method and server |
| CN111680100B (en) * | 2020-04-30 | 2023-02-28 | 聚好看科技股份有限公司 | Redis data synchronization method and server |
| CN112653734A (en) * | 2020-12-11 | 2021-04-13 | 邦彦技术股份有限公司 | Server cluster real-time master-slave control and data synchronization system and method |
| CN112653734B (en) * | 2020-12-11 | 2023-09-19 | 邦彦技术股份有限公司 | Real-time master-slave control and data synchronization system and method for server cluster |
| CN112860794A (en) * | 2021-02-03 | 2021-05-28 | 百果园技术(新加坡)有限公司 | Cache-based concurrency capability improving method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107545060A (en) | A kind of method for limiting speed and device of redis principals and subordinates full dose synchrodata | |
| CN102098342B (en) | Transaction level-based data synchronizing method, device thereof and system thereof | |
| US7660866B2 (en) | Use of virtual targets for preparing and servicing requests for server-free data transfer operations | |
| CN101741911B (en) | Multi-copy collaboration-based write operation method, system and node | |
| CN107402722B (en) | Data migration method and storage device | |
| CN110502583A (en) | Distributed Data Synchronization method, apparatus, equipment and readable storage medium storing program for executing | |
| CN104965757A (en) | Virtual machine live migration method, virtual machine migration management apparatus, and virtual machine live migration system | |
| CN106227587B (en) | A kind of band snapshot virtual machine complete machine dynamic migration method and device | |
| RU2595764C2 (en) | Method and device for processing messages | |
| EP3623963A1 (en) | Log entry duplication method and device, computer equipment, and storage medium | |
| CN104536699B (en) | A kind of stream data wiring method based on embedded file system | |
| CN105589744B (en) | A kind of virtual machine migration method and device | |
| CN109492049B (en) | Data processing, block generation and synchronization method for block chain network | |
| CN110413595A (en) | A kind of data migration method and relevant apparatus applied to distributed data base | |
| CN111104069A (en) | Multi-region data processing method and device of distributed storage system and electronic equipment | |
| CN106330788B (en) | Message fragment transmission method and device | |
| EP3051408A1 (en) | Data operating method and device | |
| CN106357703B (en) | Cluster switching method and device | |
| CN107770207A (en) | The method of data syn-chronization between multi-terminal equipment | |
| CN105956032A (en) | Cache data synchronization method, system and apparatus | |
| US9460182B2 (en) | Networking-assisted input/output order preservation for data replication | |
| CN104317716A (en) | Method for transmitting data among distributed nodes and distributed node equipment | |
| EP0637155A1 (en) | Method and system for buffering transient data | |
| CN116360696B (en) | Distributed block storage system, medium, and electronic device thereof | |
| CN111984198A (en) | Message queue implementation method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20180105 |