CN111414392A - Cache asynchronous refresh method, system and computer readable storage medium - Google Patents
Cache asynchronous refresh method, system and computer readable storage medium Download PDFInfo
- Publication number
- CN111414392A CN111414392A CN202010219946.2A CN202010219946A CN111414392A CN 111414392 A CN111414392 A CN 111414392A CN 202010219946 A CN202010219946 A CN 202010219946A CN 111414392 A CN111414392 A CN 111414392A
- Authority
- CN
- China
- Prior art keywords
- cache
- database
- data
- record
- refresh
- 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
Images
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/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
- G06F16/24552—Database cache management
-
- 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/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
Abstract
A cache asynchronous refreshing method includes detecting a refreshing log table of a database cache, matching records to be processed with an SQ L characteristic table of the database cache according to table names and index information when data of a database are changed, setting an SQ L characteristic state corresponding to the records to be in refreshing according to the table names and main key information in the refreshing log table, obtaining corresponding data from the database according to the table names and the main key information in the refreshing log table, flushing the data into the database cache, setting a SQ L characteristic state corresponding to the records to be effective after the data refreshing is finished, then deleting the corresponding records in the refreshing log table, and deleting the corresponding records in the refreshing log table when the records are not matched with an SQ L characteristic.
Description
Technical Field
The invention belongs to the technical field of database caches, and particularly relates to a cache asynchronous refreshing method, a cache asynchronous refreshing device, electronic equipment and a computer readable storage medium.
Background
When the data transmission method is used in a big data era, the scale of service application is increased along with exponential increase of user data quantity, and a traditional high-performance single host system gradually evolves into a distributed system. With the change of the business application deployment architecture, the database resources which the application depends on must also adopt a way of being deployed separately from the application host. When a large amount of applications remotely and frequently access the database, the high network delay occupied by remote access can seriously reduce the processing efficiency of the system from the perspective of the application side; from the perspective of the database, with high concurrent operation of the application, a large amount of host system resources, hardware resources and network resources where the database is located are consumed, so that the stability and performance of the whole system are further weakened, and user experience is influenced. In order to improve the system efficiency of the application, a cache system is usually deployed on an application host, and hot spot data is stored in a local memory, so that the high time delay of remote database access is avoided, and meanwhile, the access pressure of the remote database host is effectively released, thereby achieving the purpose of improving the overall performance and stability of the system.
When the application uses the cache, the requirement on the validity of the cache data is higher and higher, namely the cache data is consistent with the database data. To ensure cache data validity, a synchronous or asynchronous refresh is typically used to keep the cache data consistent with the target database data.
For refreshing data in a synchronous manner, the solution in actual production is to lock the cache periodically, and poll all data in the cache to refresh the difference data from the database to the cache. The scheme can block the access of the application to the cache data periodically, and the application performance is seriously influenced.
For asynchronous data refreshing, the solution in actual production is usually to construct a data change log table, and by recording the transaction log of database operation, the data in the cache is refreshed in a targeted manner. On one hand, the scheme can not ensure that the refreshed data is the data existing in the cache, namely, a large amount of invalid operations exist in the data refreshing; on the other hand, the application cannot quickly check whether the used cache data is being refreshed, that is, the validity of the application accessing the cache cannot be guaranteed.
In the prior art, a cache data change refreshing method generally performs data refreshing by using the dimension of a table, but once part of data in a certain table is frequently changed (the rest of data is kept unchanged), the table cannot actually use a cache, so that the availability of the cache is seriously reduced; in addition, the method avoids a large amount of invalid operations in data refreshing in a mode of loading full table data when the cache is started, but introduces a large amount of redundant data which are not accessed or never accessed by application, thereby effectively wasting a large amount of host memory.
Disclosure of Invention
In view of the above-mentioned deficiencies of the prior art, it is an object of the present invention to provide a method for improved asynchronous refresh of a database cache with a high availability of the cache system and low redundancy of data.
The embodiment of the invention discloses a cache asynchronous refreshing method which comprises the steps of detecting a refreshing log table of a database cache, wherein the refreshing log table at least comprises a table name, primary key information and index information, matching records to be processed with an SQ L characteristic table of the database cache according to the table name and the index information when database data are changed, wherein the SQ L characteristic table at least comprises SQ L characteristic information used for maintaining service application, setting an SQ L characteristic state corresponding to the records to be in refreshing when the records are matched with an SQ L characteristic, obtaining corresponding data from the database according to the table name and the primary key information in the refreshing log table, refreshing the data into the database cache, setting a characteristic state corresponding to the records to be effective after the data are refreshed, then deleting the corresponding records in the refreshing log table, and deleting the corresponding records in the refreshing log table when the records are not matched with an SQ L characteristic.
In one possible embodiment, the detecting the refresh log table of the database cache in real time includes: judging whether a record to be processed exists in a refreshing log table of a database cache; if the record to be processed exists, the table name and the index field are obtained from the refresh log table.
In one possible embodiment, the method further comprises initializing the database cache by creating a cache table according to the table structure of the database, and creating the SQ L feature table and the cache flush log table when the cache tables are successfully created.
In one possible embodiment, the structure of the cache table is the same as the structure of the database table.
In one possible embodiment, when a business application accesses data, an SQ L query request of the business application is received, the request is subjected to feature analysis and at least one SQ L feature is obtained, the SQ L feature is matched with an SQ L feature table, when the feature matching is successful and the state is effective, a database cache is accessed for data query, when the feature matching is not successful, the database is accessed for data query, and the SQ L feature is recorded in an SQ L feature table.
A cache asynchronous refreshing system comprises a cache engine, a database and a database cache, wherein the database cache comprises a refreshing log table, an SQ L characteristic table and a cache table, the cache engine comprises a cache refreshing module, the cache refreshing module is configured to detect the refreshing log table, the refreshing log table at least comprises a table name, primary key information and index information, the cache engine is further configured to match records to be processed with the SQ L characteristic table according to the table name and the index information when database data are changed, the SQ L characteristic table at least comprises SQ L characteristic information used for maintaining service application, the database cache is configured to set an SQ L characteristic state corresponding to the records to be refreshed when the records are matched with an SQ L characteristic, acquire corresponding data from the database according to the table name and the primary key information in the refreshing log table and flush the data into the database cache, after the cache is finished, the SQ L characteristic state corresponding to the records is set to be refreshed, then the SQ L corresponding records in the refreshing log table is deleted, and the SQ L characteristic record is configured to be deleted as a record which is not matched with the refreshing log 84.
In one possible embodiment, the cache refreshing module is further configured to determine whether there is a pending record in a refresh log table of the database cache; if the record to be processed exists, the table name and the index field are obtained from the refresh log table.
In one possible embodiment, the database cache is further configured to create a cache table based on the table structure of the database, and to create a SQ L feature table and a cache flush log table when the cache tables are successfully created.
In one possible embodiment, when a business application accesses data, the cache engine is further configured to receive an SQ L query request for the business application, perform signature parsing on the request and obtain at least one SQ L signature, match the SQ L signature with an SQ L signature table, access the database cache to perform data queries when the signature matching is successful and the status is valid, access the database to perform data queries when the signature non-matching is successful, and record the SQ L signature in an SQ L signature table.
A computer storage medium storing a computer program which, when executed, implements the cache asynchronous refresh method according to the preceding.
Compared with the prior art, the invention has the following beneficial effects:
the method realizes high availability of cache asynchronous refreshing, controls the influence range of the cache data asynchronous refreshing process at a record level, solves the problem that the table cannot be accessed in the cache when the table data is changed and refreshed, and improves the availability of a database cache system. Meanwhile, the cache data asynchronous refreshing flow only carries out refreshing change operation on the effective data in the cache, and the performance of cache data asynchronous refreshing is improved.
In addition, when asynchronous refreshing of database data to cache data is carried out, on one hand, the changed data can be matched with the SQ L characteristic in the SQ L characteristic table, whether the changed data are in the cache or not is determined, effective data in the cache are controlled to be refreshed, the cache is prevented from being loaded with the whole amount of data to be refreshed, the performance of data change refreshing is improved, and the redundancy of cache data is reduced.
Drawings
FIG. 1 is a schematic diagram of a cache asynchronous refresh system according to an embodiment of the present invention;
FIG. 2 is a flow chart of a method according to an embodiment of the present invention;
FIG. 3 is a flow chart of asynchronous refresh of database cache data according to an embodiment of the present invention;
FIG. 4 is a flow diagram of a database cache data access according to an embodiment of the present invention;
FIG. 5 is a flowchart of database cache system initialization, according to an embodiment of the invention.
Detailed Description
In order to facilitate understanding of those skilled in the art, the present invention will be further described with reference to the following examples and drawings, which are not intended to limit the present invention.
Existing methods of cache asynchronous refresh typically implement access to cache data by applications in the dimension of a table. This approach reduces the availability of the cache system while also resulting in data redundancy and memory wastage.
Based on the above-identified problems, an embodiment of the present invention discloses a cache asynchronous refresh system and method based on SQ L feature, and the system includes a cache engine 20, a database cache 30 and a database 40 as shown in fig. 1.
The cache engine 20 can include, among other things, a SQ L signature resolution module, a signature matching module, and a cache flush module the cache engine can receive SQ L query requests from applications 10 of the business host/computing device.
The SQ L signature resolution module may read information from the SQ L signature table in the database cache.
The cache engine 20 receives the request and performs SQ L resolution by an SQ L feature resolution module to obtain one or more base queries SQ L each base query SQ L has a corresponding table name, index field value, thus forming one or more SQ L features.
The SQ L feature analysis module is mainly used for splitting a complex SQ L into an indexed general query SQ L, for example, dynamically splitting an SQ L under a OR condition into a plurality of SQ L for storage, and splitting a subquery into a plurality of basic queries.
The signature matching module may be used to check the SQ L signature table in the database cache to see if the corresponding SQ L signature can access the cache, automatically switch access to the database to retrieve data when access to the cache is not allowed and record the SQ L signature in the SQ L signature table, automatically switch access to the cache table to retrieve data when access to the cache is allowed, retrieve data from the database or cache when multiple SQ L signatures are available, and perform result set merging according to the above conditions.
The cache refreshing module can be used for detecting a refreshing log table in the database cache, controlling the characteristic state according to the detection condition and changing the cache data.
The database cache 30 may include SQ L signature tables, flush log tables, and cache tables, wherein the SQ L signature tables may include table names, index information, access times, and status fields for checking and recording the SQ L used by the application the SQ L signature tables are stored in the in-memory database the size of the SQ L signature table is scaled by the number of indexes, and the table size is maximized if and only if the index field data is not duplicated at all.
The flush log table may include a table name, primary key information, index information, and an operation type for logging database change transactions, where the table name and index information are primary keys of the SQ L profile table
The cache table structure is consistent with the database table structure, and the cache table structure is read from the database according to cache configuration after the cache service is started, and tables corresponding to the database one by one are created in the cache.
The database 40 includes tables and is used to write record changes to the refresh record table by record dimension when database data changes.
As shown in fig. 2, the embodiment of the present invention further discloses a cache asynchronous refresh method based on SQ L feature, which includes the following steps:
s10, a refresh log table of the database cache is detected, wherein the refresh log table includes a table name, primary key information, index information, and may further include an operation type field.
And detecting the refreshed log table in real time through a cache refreshing module, and judging whether the data in the database is changed. When a database transaction occurs in the database, a corresponding transaction log is written into the database cache. Specifically, whether a record to be processed exists in the refresh log table can be judged; if the record to be processed exists, the table name and the index field are obtained from the refresh log table.
And S20, when the database data is changed, matching the record to be processed with an SQ L characteristic table of the database cache according to the table name and the index information, wherein the SQ L characteristic table can comprise SQ L characteristics, states, access time, index information and the like used for maintaining applications.
When the database data is changed, the database transaction is written into the refresh log table. Specifically, as shown in fig. 3, for a certain database data change operation set, the operated transaction log is written into the cache refresh log table according to the record dimension, and i records are generated. At this time, the cache flush service checks that there are records in the flush log table to be processed, polls to access the i records, and each polling operation is counted as a flush batch.
Referring to steps 101 and 102 in fig. 3, the flow is that a foreign key (table name and index information field) is obtained in the refresh log table and matching is carried out in the SQ L feature table, because the foreign key is the primary key of the SQ L feature table, the matching relationship is unique and the matching performance is high.
S30, when the record is matched with the SQ L characteristic, setting the SQ L characteristic state corresponding to the record to be in refreshing, acquiring corresponding data from a database according to the table name and the primary key information in the refreshing log table, flushing the data into a database cache according to the operation type in the refreshing log table, and after the data refreshing is finished, setting the SQ L characteristic state corresponding to the record to be effective.
Specifically, referring to fig. 3, after the matching is completed, j records in the refresh log table are found to be matched with the SQ L characteristic, the state corresponding to the matched SQ L characteristic record is set to [ refresh in progress ], and at this time, the data are not allowed to be accessed from the cache, step 103 is to obtain unique data from the database according to the primary key (table name, primary key information) in the refresh log table, so as to refresh the operation type in the log table, and flush the data into the cache.
Wherein the operation types of the insertion and the update are refreshed into the database cache in a combined mode; the operation type for deletion is flushed into the database cache in a deleted manner.
Within a refresh batch, the SQ L signature state is reset [ validate ] if and only if there is no any data not refreshed for the SQ L signature corresponding to the SQ L signature state [ Refresh ].
And when the corresponding refreshing operation is finished, deleting the corresponding record in the refreshing log table. Not deleting records in the refresh log table at this time may result in repeated refreshes, affecting performance.
And S40, when the record does not match the SQ L characteristic, deleting the corresponding record in the refresh log table.
Specifically, referring to FIG. 3, step 104, the flow process is performed to the extent that i-j records in the flush log table fail to match the SQ L characteristic, and the data is not accessed before the application.
The method can control the influence range of asynchronous refreshing by recording the dimension, when a certain piece of data is refreshed from a physical library to the cache, the normal access of the rest data in the cache is not influenced, and the high availability of the cache system is greatly improved.
The asynchronous refreshing method also comprises the steps of initializing the cache system before cache data access and cache data refreshing, initializing the database cache, namely creating a cache table according to the table structure of the database, and creating an SQ L characteristic table and a cache refreshing log table after the cache table is successfully created.
Specifically, fig. 4 is a flowchart of database cache system initialization based on the SQ L feature according to an embodiment of the present invention, after a cache service is started, a corresponding table structure is read from a remote database according to cache configuration and is established in a local cache, if and only if all configured cache tables are successfully established, an SQ L feature table and a cache refresh log table are established, the SQ L feature table and the cache refresh log table are system tables, and it is not necessary to read the table structure from the remote database.
Note that the established table structure contains fields, primary keys and indexes that the application needs to access, and does not need to load the full amount of data in the database table.
The method also comprises the specific steps of data access by an application, the application accesses a cache through a cache engine when data access is carried out, the cache engine analyzes an application SQ L request to obtain one or more SQ L characteristics and carries out matching in an SQ L characteristic table, when a certain SQ L characteristic is completely matched with records in the SQ L characteristic table and the state is effective, the cache can be accessed and the data meeting the conditions is returned to the application, otherwise, the SQ L characteristic is recorded in the SQ L characteristic table and the state is to be generated and the database is switched to access the data through cache driving, and the cache engine realizes the functions of transparent switching between the database and the cache and combination of multiple SQ L characteristic query data sets.
Specifically, FIG. 5 is a flow chart of database cache data access based on SQ L characteristics according to the present invention, an application uses a complex multi-characteristic SQ L to perform data access, the SQ L is transmitted to a cache engine to perform SQ L analysis, N SQ L characteristics are obtained, different SQ L characteristics are reflected in that the used index fields and index values are different, and the same table is accessed.
In step 301, the N SQ L signatures are matched in the SQ L signature table to obtain N1One matches in SQ L signature table and status is effective]Is characterized by N2One matches in SQ L signature table and state is [ in flush ]]Is characterized by N3One matched in SQ L feature table and state is [ pending for validation ]]Is characterized by N4Features that do not match in the SQ L feature table.
One SQ L in this embodiment relates to the multiple SQ L feature, which also has an effect of improving system performance as long as some features use local cache access1、N2、N3、N4Rather than representing the number of data actually accessed last, the representation of the different SQ L features in this embodiment enables the system to control the record dimension, i.e. [ validate]Cache data corresponding to SQ L feature of state, not subject to NOT [ validate ]]SQ L characteristic impact of the state, thereby achieving high availability of the system1、N2、N3、N4Corresponding to step 302, step 303, step 304, and step 305, respectively.
Step 302 is a scenario where the matching SQ L feature status is [ valid ], at which point the data access can be read directly from the database cache.
When the corresponding SQ L feature uses the index, the corresponding SQ L feature is inserted into an SQ L feature table, after the SQ L feature state is set to be effective, the remote database is switched to access data, the returned data is collected into a cache, when and only when all the data of the query at this time are collected into the cache, the SQ L feature state using the index is set to be effective, when the corresponding SQ L feature does not use the index, the remote database is directly switched to access the data, and the result set returned by the remote database is not cached.
Step 306 is a scenario of merging multi-feature SQ L query result sets, and when application access SQ L is a single feature, no result set merging needs to be done.
The embodiment of the invention is based on SQ L characteristics, and can accurately match data accessed by an application by constructing an SQ L characteristic table, realize row-level data control, and refine the access operation of the application from table dimension to record dimension.
It will be appreciated that the above methods are all implemented in a computer program capable of running on the L INUX, AIX, HP, and WINDOWS operating systems and are not dependent on the software onboard the operating systems.
In the several embodiments provided in the present application, it should be understood that the disclosed system and method may be implemented in other ways. For example, the above-described embodiments are merely illustrative, and for example, a division of a unit is merely a division of a logic function, and an actual implementation may have another division, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed.
Units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present invention.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
While the invention has been described in terms of its preferred embodiments, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention.
Claims (10)
1. A cache asynchronous refresh method is characterized in that,
detecting a refresh log table of a database cache, wherein the refresh log table at least comprises a table name, primary key information and index information;
when the database data is changed, matching the record to be processed with an SQ L characteristic table of a database cache according to the table name and the index information, wherein the SQ L characteristic table at least comprises SQ L characteristic information used for maintaining service application use;
when the record is matched with the SQ L characteristic, setting the SQ L characteristic state corresponding to the record as in refresh, acquiring corresponding data from a database according to the table name and the primary key information in a refresh log table, and flushing the data into a database cache, and after the data refresh is finished, setting the SQ L characteristic state corresponding to the record as effective, and then deleting the corresponding record in the refresh log table;
when the record does not match the SQ L signature, the corresponding record in the flush log table is deleted.
2. The method of claim 1, wherein detecting in real-time a refresh log table of a database cache comprises: judging whether a record to be processed exists in a refreshing log table of a database cache; if the record to be processed exists, the table name and the index field are obtained from the refresh log table.
3. The method as recited in claim 1, wherein the method is preceded by initializing the database cache by creating a cache table based on a table structure of the database, and creating the SQ L feature table and the cache flush log table when the cache table creation is successful.
4. The method of claim 3, wherein the structure of the cache table is the same as the structure of the database table.
5. The method of claim 1, wherein when a business application accesses data, receiving a SQ L query request for the business application, performing signature parsing on the request and obtaining at least one SQ L signature, matching the SQ L signature with an SQ L signature table, when signature matching is successful and the status is valid, accessing a database cache for data query, when signature non-matching is successful, accessing a database for data query, and recording the SQ L signature in an SQ L signature table.
6. A cache asynchronous refresh system is characterized by comprising a cache engine, a database and a database cache, wherein the database cache comprises a refresh log table, an SQ L characteristic table and a cache table;
the cache engine comprises a cache refreshing module configured to detect a refresh log table, wherein the refresh log table at least comprises a table name, primary key information and index information;
the cache engine is further configured to match the record to be processed with an SQ L feature table according to the table name and index information when database data changes, wherein the SQ L feature table at least comprises SQ L feature information for maintaining business application usage;
the database cache is configured to set the SQ L characteristic state corresponding to the record to be in refreshing when the record is matched with the SQ L characteristic, acquire corresponding data from the database according to the table name and the primary key information in the refreshing log table and flush the data into the database cache;
the database cache is further configured to delete a corresponding record in the flush log table when the record does not match the SQ L signature.
7. The system of claim 6, wherein the cache flush module is further configured to determine whether there are pending records in a flush log table of the database cache; if the record to be processed exists, the table name and the index field are obtained from the refresh log table.
8. The system as recited in claim 6, wherein the database cache is further configured to create a cache table based on the table structure of the database, and when the cache table is successfully created, create an SQ L feature table and a cache flush log table.
9. The system of claim 6, wherein when a business application accesses data, the cache engine is further configured to receive a SQ L query request for the business application, perform feature resolution on the request and obtain at least one SQ L feature, match the SQ L feature with an SQ L feature table, access the database cache for a data query when a feature match is successful and the status is valid, access the database for a data query when a feature mismatch is successful and record the SQ L feature in an SQ L feature table.
10. A computer storage medium storing a computer program, characterized in that the computer program, when executed, implements the cache asynchronous refresh method according to any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010219946.2A CN111414392B (en) | 2020-03-25 | 2020-03-25 | Cache asynchronous refresh method, system and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010219946.2A CN111414392B (en) | 2020-03-25 | 2020-03-25 | Cache asynchronous refresh method, system and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111414392A true CN111414392A (en) | 2020-07-14 |
| CN111414392B CN111414392B (en) | 2022-08-05 |
Family
ID=71491485
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010219946.2A Active CN111414392B (en) | 2020-03-25 | 2020-03-25 | Cache asynchronous refresh method, system and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111414392B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111931094A (en) * | 2020-07-16 | 2020-11-13 | 北京首汽智行科技有限公司 | Dynamic synchronization method for cache data |
| CN112749197A (en) * | 2021-01-12 | 2021-05-04 | 中国平安财产保险股份有限公司 | Data fragment refreshing method, device, equipment and storage medium |
| CN113032344A (en) * | 2020-08-25 | 2021-06-25 | 广州锦行网络科技有限公司 | Method for cleaning remote login log records |
| CN113742381A (en) * | 2021-08-30 | 2021-12-03 | 欧电云信息科技(江苏)有限公司 | Cache acquisition method, apparatus and computer readable medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020123978A1 (en) * | 1999-09-22 | 2002-09-05 | Paul Miller Bird | Method and apparatus for cross-node sharing of cached dynamic sql in a multiple relational database management system environment |
| US20040010499A1 (en) * | 2002-07-02 | 2004-01-15 | Sybase, Inc. | Database system with improved methods for asynchronous logging of transactions |
| CN102508854A (en) * | 2011-09-29 | 2012-06-20 | 畅捷通信息技术股份有限公司 | Data access device and method |
| CN103827865A (en) * | 2011-09-23 | 2014-05-28 | 国际商业机器公司 | Improving database caching utilizing asynchronous log-based replication |
| US20140317047A1 (en) * | 2013-04-22 | 2014-10-23 | Sap Ag | Enhanced transactional cache with bulk operation |
| CN104572689A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Data synchronizing method, device and system |
| CN105324770A (en) * | 2013-04-30 | 2016-02-10 | 亚马逊科技公司 | Efficient read replicas |
| CN108334505A (en) * | 2017-01-19 | 2018-07-27 | 阿里巴巴集团控股有限公司 | A kind of data processing method, device, server and inventory system |
| CN108811271A (en) * | 2018-04-28 | 2018-11-13 | 上海与德科技有限公司 | A kind of light adjusting method, device, intelligent desk lamp and storage medium |
| CN110597909A (en) * | 2019-09-12 | 2019-12-20 | 广州南翼信息科技有限公司 | Method for keeping state consistency of client and multi-terminal equipment |
-
2020
- 2020-03-25 CN CN202010219946.2A patent/CN111414392B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020123978A1 (en) * | 1999-09-22 | 2002-09-05 | Paul Miller Bird | Method and apparatus for cross-node sharing of cached dynamic sql in a multiple relational database management system environment |
| US20040010499A1 (en) * | 2002-07-02 | 2004-01-15 | Sybase, Inc. | Database system with improved methods for asynchronous logging of transactions |
| CN103827865A (en) * | 2011-09-23 | 2014-05-28 | 国际商业机器公司 | Improving database caching utilizing asynchronous log-based replication |
| CN102508854A (en) * | 2011-09-29 | 2012-06-20 | 畅捷通信息技术股份有限公司 | Data access device and method |
| US20140317047A1 (en) * | 2013-04-22 | 2014-10-23 | Sap Ag | Enhanced transactional cache with bulk operation |
| CN105324770A (en) * | 2013-04-30 | 2016-02-10 | 亚马逊科技公司 | Efficient read replicas |
| CN104572689A (en) * | 2013-10-17 | 2015-04-29 | 腾讯科技（深圳）有限公司 | Data synchronizing method, device and system |
| CN108334505A (en) * | 2017-01-19 | 2018-07-27 | 阿里巴巴集团控股有限公司 | A kind of data processing method, device, server and inventory system |
| CN108811271A (en) * | 2018-04-28 | 2018-11-13 | 上海与德科技有限公司 | A kind of light adjusting method, device, intelligent desk lamp and storage medium |
| CN110597909A (en) * | 2019-09-12 | 2019-12-20 | 广州南翼信息科技有限公司 | Method for keeping state consistency of client and multi-terminal equipment |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111931094A (en) * | 2020-07-16 | 2020-11-13 | 北京首汽智行科技有限公司 | Dynamic synchronization method for cache data |
| CN113032344A (en) * | 2020-08-25 | 2021-06-25 | 广州锦行网络科技有限公司 | Method for cleaning remote login log records |
| CN112749197A (en) * | 2021-01-12 | 2021-05-04 | 中国平安财产保险股份有限公司 | Data fragment refreshing method, device, equipment and storage medium |
| CN112749197B (en) * | 2021-01-12 | 2024-04-05 | 中国平安财产保险股份有限公司 | Data fragment refreshing method, device, equipment and storage medium |
| CN113742381A (en) * | 2021-08-30 | 2021-12-03 | 欧电云信息科技(江苏)有限公司 | Cache acquisition method, apparatus and computer readable medium |
| CN113742381B (en) * | 2021-08-30 | 2023-07-25 | 欧电云信息科技(江苏)有限公司 | Cache acquisition method, device and computer readable medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111414392B (en) | 2022-08-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111414392B (en) | Cache asynchronous refresh method, system and computer readable storage medium | |
| US8429134B2 (en) | Distributed database recovery | |
| CN101567805B (en) | Method for recovering failed parallel file system | |
| US8645319B2 (en) | Information processing system, data update method and data update program | |
| US20200133800A1 (en) | Key-value store on persistent memory | |
| US9053153B2 (en) | Inter-query parallelization of constraint checking | |
| US20060074847A1 (en) | Method and system for data processing with data replication for the same | |
| US8793441B2 (en) | System, method and computer program product for managing data using a write-back cache unit | |
| CN105556520A (en) | Mirroring, in memory, data from disk to improve query performance | |
| US9922086B1 (en) | Consistent query of local indexes | |
| US20180218023A1 (en) | Database concurrency control through hash-bucket latching | |
| JP7101566B2 (en) | Multiversion Concurrency Control (MVCC) in non-volatile memory | |
| EP2336901B1 (en) | Online access to database snapshots | |
| WO2007063945A1 (en) | System for enhancing access efficiency to data base and its method | |
| CN111475519B (en) | Data caching method and device | |
| CN105354046B (en) | Database update processing method and system based on shared disk | |
| US20040093332A1 (en) | Method and system for reducing host variable impact on access path selection | |
| CN107888687B (en) | Proxy client storage acceleration method and system based on distributed storage system | |
| KR101806394B1 (en) | A data processing method having a structure of the cache index specified to the transaction in a mobile environment dbms | |
| US7801866B1 (en) | Systems and methods for reading only durably committed data in a system that otherwise permits lazy commit of transactions | |
| US7240065B2 (en) | Providing mappings between logical time values and real time values | |
| EP2064633B1 (en) | System, method and computer program product for managing data | |
| US20210089401A1 (en) | Method, Server, and Computer Readable Medium for Index Recovery Using Index Redo Log | |
| US10838947B2 (en) | Consistency check for foreign key definition | |
| US7251660B2 (en) | Providing mappings between logical time values and real time values in a multinode system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |