CN105808643A - Method for refreshing Redis memory database - Google Patents
Method for refreshing Redis memory database Download PDFInfo
- Publication number
- CN105808643A CN105808643A CN201610103284.6A CN201610103284A CN105808643A CN 105808643 A CN105808643 A CN 105808643A CN 201610103284 A CN201610103284 A CN 201610103284A CN 105808643 A CN105808643 A CN 105808643A
- Authority
- CN
- China
- Prior art keywords
- data
- redis
- master
- slave
- oracle
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a method for refreshing a Redis memory database, belonging to the field of data management; the Oracle-Redis is used as a system writing base and a reading base to write incremental data into Redis, the Redis is used as the system reading base, data synchronization is carried out aiming at different data reading and querying scenes, and master-slave data synchronization of the Oracle-Redis is carried out; the invention realizes the read-write separation, the Oracle database is used as a written-in database, and the Redis is used as a read database, thereby effectively improving the query and read speed of the data; the problem of data synchronization of Oracle-Reids and Redis is solved, system load is reduced, query reading speed of data is improved, influence on product performance is reduced, and high availability of the system is enhanced.
Description
Technical field
The present invention discloses a kind of method of Redis internal storage data bank refresh, belongs to data management field.
Background technology
At present mobile network management product A cross PM uses oracle database, Oracle is relevant database, High Performance Data Query can be carried out, but it is the needs meeting report query and background process, simultaneously in order to reduce oracle database pressure, Redis memory database technology can be used, as data cached storage data base.Oracle is relevant database, Redis is K/V data base, the application that both have nothing in common with each other is little to contrast, although Redis performance is higher than Oracle, but it sacrifices the most useful function simultaneously, so to be extremely difficult with Redis fallback relationship type data base completely, the mutual tonifying for the deficiency of use but both can coexist.Oracle database as the data base read, accomplishes read and write abruption as the data base of write, Redis.This problem relating to data syn-chronization, and synchronize to include the data syn-chronization of two aspect: Oracle-Reids and principal and subordinate's data syn-chronization of Redis, current Redis memory database is that full dose synchronizes with the method for synchronization of oracle database, but the reading inquiry velocity of full dose synchrodata is relatively slow, affects the performance of properties of product.The present invention provides a kind of method of Redis internal storage data bank refresh, it is achieved read and write abruption, and oracle database as the data base read, is effectively improved the inquiry reading speed of data as the data base of write, Redis；Solve the data synchronization problems of Oracle-Reids and Redis self, alleviate system load, promote the inquiry reading speed of data, reduce the impact on properties of product, strengthen the high availability of system.
Redis uses ANSI C to write, support network, can based on internal memory also can the log type of persistence, key-value data base, and provide the API of multiple beforehand research.Data in EMS memory can be written to disk to prevent loss of data at interval of certain time by Redis.Redis supports two kinds of persistence modes at present: Snapshotting(snapshot) also it is default behavior, can be by the way of configuring and arranging and automatically do snapshot persistence；Append-only file, is abbreviated as the mode of aof, and aof has more preferable persistence than snap shot, and when using aof persistence mode, the write order that each is received by Redis is appended in file by write function.The content of whole data base can be rebuild in internal memory by re-executing the write order preserved in file when Redis is restarted.
Summary of the invention
The present invention provides a kind of method of Redis internal storage data bank refresh, it is achieved read and write abruption, and oracle database is as the data base of write, and Redis, as the data base read, is effectively improved the inquiry reading speed of data, strengthens the availability of system.
The concrete scheme that the present invention proposes is:
A kind of method of Redis internal storage data bank refresh, Oracle-Redis writes storehouse and reading storehouse as system and incremental data is write Redis, Redis, as the reading storehouse of system, carries out data syn-chronization for different digital independent inquiry scenes, and carries out the principal and subordinate's data syn-chronization of self:
Oracle-Redis utilizes Pub/Sub function to replicate incremental data to multiple Redis, and Redis read Cooley with Master end write data time, start Slave end process, it sends a SYNC Command to Master, request synchronized links, data snapshot is saved in data file by Master, Master records the order of all modifications data and caches in the data file simultaneously, after completing caching, Master sends data file to Slave end, Slave performs identical operation and guarantees data consistent, it is achieved principal and subordinate's data syn-chronization.
Redis, as the reading storehouse of system, inquires about common application scenarios for digital independent, first judges in Redis whether data exist, if it does, the data that directly return cache is good；Otherwise go in data base, read data, and in data buffer storage to Redis.
Described Redis, as the reading storehouse of system, inquires about big data for digital independent and frequently changes scene, first judge in Redis whether data exist, if it does, directly update corresponding data and the data after updating are returned；Otherwise content in first more new database, then in data preservation portion to Redis.
When described Redis reads Cooley Master end write data, the SYNC Command that the corresponding multiple Slaves of same Master send, ask synchronized links, Master starts a process and preserves data file, is subsequently transmitted to all of Slave.
The plurality of Slave provides the redundancy of read-only inquiry and data, and Master end provides write operation specially.
Slave under Master accepts link and the synchronization request of other Slave in same framework, and the cascade carrying out data replicates.
Usefulness of the present invention is:
nullIn the present invention, Oracle-Redis writes storehouse and reading storehouse as system and incremental data is write Redis，Redis is as the reading storehouse of system，Data syn-chronization is carried out for different digital independent inquiry scenes，And carry out the principal and subordinate's data syn-chronization of self: Oracle-Redis and utilize Pub/Sub function to replicate incremental data to multiple Redis，And Redis read Cooley with Master end write data time，Start Slave end process，It sends a SYNC Command to Master，Request synchronized links，Data snapshot is saved in data file by Master，Master records the order of all modifications data and caches in the data file simultaneously，After completing caching，Master sends data file to Slave end，Slave performs identical operation and guarantees data consistent，Realize principal and subordinate's data syn-chronization and realize read and write abruption，Oracle database is as the data base of write，Redis is as the data base read，It is effectively improved the inquiry reading speed of data；Solve the data synchronization problems of Oracle-Reids and Redis self, alleviate system load, promote the inquiry reading speed of data, reduce the impact on properties of product, strengthen the high availability of system.
Accompanying drawing explanation
Fig. 1 Oracle-Redis of the present invention database application layer synchronizes schematic diagram；
Fig. 2 Redis of the present invention memory database application scenarios one schematic diagram；
Fig. 3 Redis of the present invention memory database application scenarios two schematic diagram；
Fig. 4 Redis of the present invention read and write abruption process schematic.
Detailed description of the invention
In conjunction with accompanying drawing, the present invention will be further described.
A kind of method of Redis internal storage data bank refresh, Oracle-Redis writes storehouse and reading storehouse as system and incremental data is write Redis, Redis, as the reading storehouse of system, carries out data syn-chronization for different digital independent inquiry scenes, and carries out the principal and subordinate's data syn-chronization of self:
Oracle-Redis utilizes Pub/Sub function to replicate incremental data to multiple Redis, and Redis read Cooley with Master end write data time, start Slave end process, it sends a SYNC Command to Master, request synchronized links, data snapshot is saved in data file by Master, Master records the order of all modifications data and caches in the data file simultaneously, after completing caching, Master sends data file to Slave end, data file can be saved on hard disk by Slave end, then by it in being loaded into internal memory, Slave can perform identical operation and guarantee data consistent, realize principal and subordinate's data syn-chronization.
In above-mentioned digital independent inquiry scene, when inquiring about common application scenarios for digital independent, applicable data amount is bigger, but it not the most more news, first judge whether key exists, i.e. first in Redis, judge whether data exist, if it does, the data that directly return cache is good；Otherwise go in data base, read data, and in data buffer storage to Redis；
Inquire about big data for digital independent and frequently change scene, it is suitable for the most more news, first judge whether key exists, i.e. first in Redis, judge whether data exist, if there is, directly update corresponding data and the data after updating are returned, such as corresponding updated key is recorded, be saved in redis, retrieval information during convenient synchronization, key can be save_update_keys, and the data after updating are returned；Otherwise content in first more new database, then preserves data a in Redis, and the key that backstage stores the save_update_keys in Redis reads out respectively, finds the data of correspondence, in renewal to data base.
Wherein Redis reads Cooley Master end and writes data, same Master can the SYNC Command that sends of corresponding multiple Slaves, ask synchronized links, Master starts process and preserves data file, is subsequently transmitted to all of Slave.If Slave breaks down causes the machine of delaying, can automatically reconnect after recovering normally, after Master receives the connection of Slave, the data file that it is complete is sent to Slave.The form of multiple Slave is conducive to provide the redundancy of read-only inquiry and data, and Master end provides write operation specially, accomplishes read and write abruption.See accompanying drawing 4.
And the Slave under Master accepts link and the synchronization request of other Slave in same framework, the cascade carrying out data replicates.
When carrying out principal and subordinate's data syn-chronization of specifically Redis self, Slave server is connected to Master server, and when sending SYNC order, Slave server connects Master server by sync With Master () function, and send SYNC command request to synchronize, then rdb file is opened, the data sended over by Master for storage, create the I/O event reading rdb.Code is as follows:
int syncWithMaster(void) {
// log in master server
if(server.masterauth) {
syncWrite(fd, "AUTH xxx\r\n",
strlen(server.masterauth)+7, 5);
}
// send SYNC order
syncWrite(fd,"SYNC \r\n",7,5);
// open rdb file
dfd = open(tmpfile,O_CREAT|O_WRONLY|O_EXCL,0644);
// create the I/O event reading rdb
aeCreateFileEvent(server.el, fd, AE_READABLE,
readSyncBulkPayload, NULL);
return REDIS_OK;
}
And Master server backup data base is in .rdb file, when Slave server sends SYNC order to Master server, Master server will call sync Command () function and synchronize.The first step synchronized is that the data of data base are stored as rdb file, calls update Slaves Waiting Bgsave () function to send rdb file to all of Slave server after storage.Code is as follows:
void syncCommand(redisClient *c) {
If // preserving rdb file
if (server.bgsavechildpid != -1) {
// mainly judge that currently stored rdb file is by SYNC command triggers
If // currently stored rdb file is not by SYNC command triggers, then to wait until next time
Else // otherwise call rdbSaveBackground () storage rdb file
rdbSaveBackground(server.dbfilename);
}
}
When rdbSaveBackground () function is finished, will call updateSlavesWaitingBgsave () and send rdb file to all of Slave server, code is as follows:
void updateSlavesWaitingBgsave(int bgsaveerr) {
listRewind(server.slaves,&li);
while((ln = listNext(&li))) {
slave->repldbfd
= open(server.dbfilename,O_RDONLY);
aeCreateFileEvent(server.el,slave->fd,AE_WRITABLE,
sendBulkToSlave,slave);
}
}
Update Slaves Waiting Bgsave () opens rdb file, creates and sends rdb file I/O event, and send Bulk To Slave () is mainly sent to Slave server rdb file.After Slave server reception rdb file is complete, the data of original data base can be emptied, then the data of rdb file are imported in data base.
Increment synchronization: after completing above step, synchronizes to be basically completed, and when Master server has data to update when, can be synchronized to all of Slave server at once.Completed by replication Feed Slaves () function.When Master server increase and decrease data when, will trigger replication Feed Slaves (), code is as follows:
void call(redisClient *c, struct redisCommand *cmd) {
if
((dirty ||
cmd->flags & REDIS_CMD_FORCE_REPLICATION) &&
listLength(server.slaves))
replicationFeedSlaves(server.slaves,c->db->id,c->argv,c->argc);
}
Call () function is exactly to trigger when user is exectorial time, and dirty has indicated whether that data update, if having data to update and slave server is for empty, is carried out replication Feed Slaves ().And the order that the work that replication Feed Slaves () mainly does performs user exactly is sent to all of Slave server, Slave server is allowed to perform.Implement synchronizing function.
Additionally, Oracle-Redis utilizes Pub/Sub function, i.e. issue and subscribe to function.In system based on event, use event as basic communication mechanism, it is provided that the loosely-coupled interactive mode required by large scale system: subscriber, as client gives expression to its interesting event received or a class event in the way of event subscription；Publisher, as event interested for subscriber can be notified relevant subscriber by server at any time.Utilizing Pub/Sub function, multiple Redis, as subscriber, can accept incremental data.
Claims (6)
1. the method for a Redis internal storage data bank refresh, it is characterized in that Oracle-Redis writes storehouse and reading storehouse as system and incremental data is write Redis, Redis, as the reading storehouse of system, carries out data syn-chronization for different digital independent inquiry scenes, and carries out the principal and subordinate's data syn-chronization of self:
Oracle-Redis utilizes Pub/Sub function to replicate incremental data to multiple Redis, and Redis read Cooley with Master end write data time, start Slave end process, it sends a SYNC Command to Master, request synchronized links, data snapshot is saved in data file by Master, Master records the order of all modifications data and caches in the data file simultaneously, after completing caching, Master sends data file to Slave end, Slave performs identical operation and guarantees data consistent, it is achieved principal and subordinate's data syn-chronization.
Method the most according to claim 1, is characterized in that the Redis reading storehouse as system, inquires about common application scenarios for digital independent, first judges in Redis whether data exist, if it does, the data that directly return cache is good；Otherwise go in data base, read data, and in data buffer storage to Redis.
Method the most according to claim 1, it is characterized in that the described Redis reading storehouse as system, inquire about big data for digital independent and frequently change scene, first in Redis, judge whether data exist, if it does, directly update corresponding data and the data after updating returned；Otherwise content in first more new database, then in data preservation portion to Redis.
4. according to the method described in any one of claim 1-3, it is characterized in that when described Redis reads Cooley Master end write data, the SYNC Command that the corresponding multiple Slaves of same Master send, request synchronized links, Master starts a process and preserves data file, is subsequently transmitted to all of Slave.
Method the most according to claim 4, is characterized in that the plurality of Slave provides the redundancy of read-only inquiry and data, and Master end provides write operation specially.
Method the most according to claim 4, is characterized in that the Slave under Master accepts link and the synchronization request of other Slave in same framework, and the cascade carrying out data replicates.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610103284.6A CN105808643A (en) | 2016-02-25 | 2016-02-25 | Method for refreshing Redis memory database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610103284.6A CN105808643A (en) | 2016-02-25 | 2016-02-25 | Method for refreshing Redis memory database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105808643A true CN105808643A (en) | 2016-07-27 |
Family
ID=56466492
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610103284.6A Pending CN105808643A (en) | 2016-02-25 | 2016-02-25 | Method for refreshing Redis memory database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105808643A (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106487948A (en) * | 2016-12-26 | 2017-03-08 | 上海斐讯数据通信技术有限公司 | A kind of DHCP service management system and DHCP service management method |
| CN107273419A (en) * | 2017-05-11 | 2017-10-20 | 广东网金控股股份有限公司 | A kind of system reads data method and device |
| CN107506378A (en) * | 2017-07-20 | 2017-12-22 | 阿里巴巴集团控股有限公司 | The implementation method and device of database access |
| CN107895253A (en) * | 2017-10-25 | 2018-04-10 | 北京科东电力控制系统有限责任公司 | A kind of method that electricity transaction function carries out micro services transformation |
| CN108288133A (en) * | 2017-01-09 | 2018-07-17 | 北京京东尚科信息技术有限公司 | The method, apparatus and system of the convenience-for-people quick dispatching cargo of self-carry point |
| CN108304408A (en) * | 2017-01-12 | 2018-07-20 | 中国移动通信集团公司 | A kind of data cached method for refreshing and device |
| CN109063066A (en) * | 2018-07-20 | 2018-12-21 | 中国邮政储蓄银行股份有限公司 | Data query method and device, data management system |
| CN109144604A (en) * | 2018-08-02 | 2019-01-04 | 山东浪潮通软信息科技有限公司 | A kind of caching process method based on Redis |
| CN109491988A (en) * | 2018-11-05 | 2019-03-19 | 北京中安智达科技有限公司 | A kind of data real time correlation method for supporting full dose to update |
| CN110175146A (en) * | 2019-04-13 | 2019-08-27 | 深圳市同泰怡信息技术有限公司 | Hard disk information acquisition methods and the device for obtaining hard disk information |
| CN110362625A (en) * | 2019-05-30 | 2019-10-22 | 杭州数梦工场科技有限公司 | Data base read-write separation method, device, electronic equipment and storage medium |
| CN111026764A (en) * | 2019-12-13 | 2020-04-17 | 上海米哈游网络科技股份有限公司 | Data storage method and device, electronic product and storage medium |
| CN111221861A (en) * | 2019-12-31 | 2020-06-02 | 武汉中海庭数据技术有限公司 | Method and device for data synchronization between local cache and database |
| CN111325494A (en) * | 2018-12-14 | 2020-06-23 | 北京京东尚科信息技术有限公司 | Inventory management method, device, system and storage medium |
| CN111522880A (en) * | 2020-04-24 | 2020-08-11 | 桂林电子科技大学 | Method for improving data read-write performance based on mysql database cluster |
| CN111538463A (en) * | 2020-04-30 | 2020-08-14 | 电子科技大学 | A Method for Realizing In-Memory Database Persistence |
| CN111666305A (en) * | 2020-06-05 | 2020-09-15 | 福建天晴在线互动科技有限公司 | Method and system for realizing association between redis cache and database |
| CN112380472A (en) * | 2020-11-13 | 2021-02-19 | 浪潮电子信息产业股份有限公司 | Visual view method and system based on Redis |
| CN118568114A (en) * | 2024-07-31 | 2024-08-30 | 济南浪潮数据技术有限公司 | Cache refresh method, device, equipment, computer program product and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110185227A1 (en) * | 2005-07-20 | 2011-07-28 | Siew Yong Sim-Tang | Method and system for virtual on-demand recovery for real-time, continuous data protection |
| CN103984715A (en) * | 2014-05-08 | 2014-08-13 | 武汉库百网络技术有限公司 | Data synchronizing and checking method, device and system of isomerous database |
| CN104572689A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Data synchronizing method, device and system |
| CN104881494A (en) * | 2015-06-12 | 2015-09-02 | 北京奇虎科技有限公司 | Method, device and system for performing data synchronization with Redis server |
| CN105005618A (en) * | 2015-07-21 | 2015-10-28 | 杭州合众数据技术有限公司 | Data synchronization method and system among heterogeneous databases |
| CN105260376A (en) * | 2015-08-17 | 2016-01-20 | 北京京东尚科信息技术有限公司 | Method, device and system for cluster node scaling |
-
2016
- 2016-02-25 CN CN201610103284.6A patent/CN105808643A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110185227A1 (en) * | 2005-07-20 | 2011-07-28 | Siew Yong Sim-Tang | Method and system for virtual on-demand recovery for real-time, continuous data protection |
| CN104572689A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Data synchronizing method, device and system |
| CN103984715A (en) * | 2014-05-08 | 2014-08-13 | 武汉库百网络技术有限公司 | Data synchronizing and checking method, device and system of isomerous database |
| CN104881494A (en) * | 2015-06-12 | 2015-09-02 | 北京奇虎科技有限公司 | Method, device and system for performing data synchronization with Redis server |
| CN105005618A (en) * | 2015-07-21 | 2015-10-28 | 杭州合众数据技术有限公司 | Data synchronization method and system among heterogeneous databases |
| CN105260376A (en) * | 2015-08-17 | 2016-01-20 | 北京京东尚科信息技术有限公司 | Method, device and system for cluster node scaling |
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106487948A (en) * | 2016-12-26 | 2017-03-08 | 上海斐讯数据通信技术有限公司 | A kind of DHCP service management system and DHCP service management method |
| CN108288133A (en) * | 2017-01-09 | 2018-07-17 | 北京京东尚科信息技术有限公司 | The method, apparatus and system of the convenience-for-people quick dispatching cargo of self-carry point |
| CN108304408A (en) * | 2017-01-12 | 2018-07-20 | 中国移动通信集团公司 | A kind of data cached method for refreshing and device |
| CN108304408B (en) * | 2017-01-12 | 2021-04-02 | 中国移动通信集团公司 | Method and device for refreshing cache data |
| CN107273419A (en) * | 2017-05-11 | 2017-10-20 | 广东网金控股股份有限公司 | A kind of system reads data method and device |
| CN107273419B (en) * | 2017-05-11 | 2021-04-23 | 深圳市博世创兴科技有限公司 | System data reading method and device |
| CN107506378B (en) * | 2017-07-20 | 2020-06-16 | 阿里巴巴集团控股有限公司 | Method and device for realizing database access |
| CN107506378A (en) * | 2017-07-20 | 2017-12-22 | 阿里巴巴集团控股有限公司 | The implementation method and device of database access |
| CN107895253A (en) * | 2017-10-25 | 2018-04-10 | 北京科东电力控制系统有限责任公司 | A kind of method that electricity transaction function carries out micro services transformation |
| CN109063066A (en) * | 2018-07-20 | 2018-12-21 | 中国邮政储蓄银行股份有限公司 | Data query method and device, data management system |
| CN109063066B (en) * | 2018-07-20 | 2022-04-01 | 中国邮政储蓄银行股份有限公司 | Data query method and device and data management system |
| CN109144604A (en) * | 2018-08-02 | 2019-01-04 | 山东浪潮通软信息科技有限公司 | A kind of caching process method based on Redis |
| CN109491988B (en) * | 2018-11-05 | 2021-12-14 | 北京中安智达科技有限公司 | Data real-time association method supporting full-scale updating |
| CN109491988A (en) * | 2018-11-05 | 2019-03-19 | 北京中安智达科技有限公司 | A kind of data real time correlation method for supporting full dose to update |
| CN111325494A (en) * | 2018-12-14 | 2020-06-23 | 北京京东尚科信息技术有限公司 | Inventory management method, device, system and storage medium |
| CN110175146A (en) * | 2019-04-13 | 2019-08-27 | 深圳市同泰怡信息技术有限公司 | Hard disk information acquisition methods and the device for obtaining hard disk information |
| CN110362625A (en) * | 2019-05-30 | 2019-10-22 | 杭州数梦工场科技有限公司 | Data base read-write separation method, device, electronic equipment and storage medium |
| CN111026764B (en) * | 2019-12-13 | 2023-08-11 | 上海米哈游网络科技股份有限公司 | Data storage method and device, electronic product and storage medium |
| CN111026764A (en) * | 2019-12-13 | 2020-04-17 | 上海米哈游网络科技股份有限公司 | Data storage method and device, electronic product and storage medium |
| CN111221861A (en) * | 2019-12-31 | 2020-06-02 | 武汉中海庭数据技术有限公司 | Method and device for data synchronization between local cache and database |
| CN111221861B (en) * | 2019-12-31 | 2023-06-02 | 武汉中海庭数据技术有限公司 | Method and device for synchronizing local cache and database data |
| CN111522880B (en) * | 2020-04-24 | 2023-08-08 | 桂林电子科技大学 | Method for improving data read-write performance based on mysql database cluster |
| CN111522880A (en) * | 2020-04-24 | 2020-08-11 | 桂林电子科技大学 | Method for improving data read-write performance based on mysql database cluster |
| CN111538463A (en) * | 2020-04-30 | 2020-08-14 | 电子科技大学 | A Method for Realizing In-Memory Database Persistence |
| CN111666305B (en) * | 2020-06-05 | 2023-03-14 | 福建天晴在线互动科技有限公司 | Method and system for realizing correlation between redis cache and database |
| CN111666305A (en) * | 2020-06-05 | 2020-09-15 | 福建天晴在线互动科技有限公司 | Method and system for realizing association between redis cache and database |
| CN112380472A (en) * | 2020-11-13 | 2021-02-19 | 浪潮电子信息产业股份有限公司 | Visual view method and system based on Redis |
| CN118568114A (en) * | 2024-07-31 | 2024-08-30 | 济南浪潮数据技术有限公司 | Cache refresh method, device, equipment, computer program product and storage medium |
| CN118568114B (en) * | 2024-07-31 | 2024-10-11 | 济南浪潮数据技术有限公司 | Cache refreshing method, device, equipment, computer program product and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105808643A (en) | Method for refreshing Redis memory database | |
| KR102119258B1 (en) | Technique for implementing change data capture in database management system | |
| US11010262B2 (en) | Database system recovery using preliminary and final slave node replay positions | |
| CN109992628B (en) | Data synchronization method, device, server and computer readable storage medium | |
| CN111078667B (en) | Data migration method and related device | |
| US9146934B2 (en) | Reduced disk space standby | |
| US7797358B1 (en) | Methods and apparatus for continuous data protection system having journal compression | |
| US9515878B2 (en) | Method, medium, and system for configuring a new node in a distributed memory network | |
| EP2380090B1 (en) | Data integrity in a database environment through background synchronization | |
| CN102098344B (en) | Method and device for synchronizing editions during cache management and cache management system | |
| KR20200056357A (en) | Technique for implementing change data capture in database management system | |
| EP4213038A1 (en) | Data processing method and apparatus based on distributed storage, device, and medium | |
| CN107623703B (en) | Synchronization method, device and system for global transaction identifier GTID | |
| CN102999584A (en) | Electric GIS (Gas Insulated Switchgear) cross-platform spatial data service method and system | |
| US20240211488A1 (en) | Transaction commitment systems, methods, and apparatuses based on distributed database systems | |
| CN104361030A (en) | Distributed cache architecture with task distribution function and cache method | |
| CN102033930A (en) | Distributed memory database system | |
| CN103365987B (en) | Clustered database system and data processing method based on shared-disk framework | |
| CN118093592A (en) | Metadata index storage method and device for distributed object storage system | |
| WO2024109253A1 (en) | Data backup method and system, and device | |
| CN105353988A (en) | Metadata reading and writing method and device | |
| CN103019626A (en) | Storage system, method and device for controlling cluster metadata | |
| CN108536833A (en) | A kind of distributed, database and its construction method towards big data | |
| CN112699118B (en) | Data synchronization method and corresponding device, system and storage medium | |
| CN113076298A (en) | Distributed small file storage system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160727 |
|
| RJ01 | Rejection of invention patent application after publication |