CN106897288B - Service providing method and system for database - Google Patents
Service providing method and system for database Download PDFInfo
- Publication number
- CN106897288B CN106897288B CN201510955708.7A CN201510955708A CN106897288B CN 106897288 B CN106897288 B CN 106897288B CN 201510955708 A CN201510955708 A CN 201510955708A CN 106897288 B CN106897288 B CN 106897288B
- Authority
- CN
- China
- Prior art keywords
- database server
- transaction log
- master
- slave
- transaction
- 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.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/22—Arrangements for detecting or preventing errors in the information received using redundant apparatus to increase reliability
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2365—Ensuring data consistency and integrity
Abstract
The embodiment of the application relates to a service providing method of a database and a database system, wherein the method comprises the following steps: when the master database server receives a service providing request of a client, changing data in a database according to the service providing request, writing the changing information of the database into a first transaction log, and sending the first transaction log to the slave database server; when a network connection between the master database server and the slave database server is disconnected or timed out, or the number of transaction logs accumulated in the master database server and which are not successfully transmitted exceeds a preset value, or the transmission time of the first transaction log exceeds a preset time, the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer. Therefore, in the embodiment of the application, when the standby library cannot receive the log temporarily, the main library sends the log to the buffer area, so that the log is ensured not to be lost.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and system for providing services to a database.
Background
Currently, database systems generally employ a master-slave architecture to provide high availability services. Normally, the main database server serves the outside. If a process of an external service performs a change to data, the change is written to the transaction log before being written to the database store. Each log records modifications to a data record, including the primary key of the data record and specific information for the update operation. The logs generated by the master database server are continuously transmitted to the slave database server through network connection. After receiving the log from the database server, the log is played back so that the data of the log is synchronized with the data of the master database server. For the sake of convenience of description, in the following description, the master database server is sometimes simply referred to as a master library, and the slave database server is sometimes simply referred to as a slave library.
In the prior art, when a database system provides services for a database to the outside, when the main library is in a downtime state or other abnormal states and cannot provide the services to the outside, the database system needs to be switched to a standby library, and the standby library continues to provide the services, so that high availability is realized. In order to make the state of the standby library consistent with the final state of the main library after switching, it is required to ensure that the standby library already has all logs of the main library.
As can be seen from the above, in the method for providing a database service in the prior art, in a master-slave architecture, a phenomenon that a log cannot be timely sent to a backup repository due to network instability (e.g., data packet loss), a network bottleneck, or the backup repository reaching a performance bottleneck (e.g., CPU utilization reaches a peak) often occurs between a master and a slave, which may cause log loss.
Disclosure of Invention
The embodiment of the application provides a service providing method and system for a database, which can ensure that logs are not lost.
In one aspect, a method for providing a service to a database is provided, where the method includes:
when a master database server receives a service providing request of a client, changing data in a database according to the service providing request, writing the changing information of the database into a first transaction log, and sending the first transaction log to a slave database server;
when the network connection between the master database server and the slave database server is disconnected or is overtime, or the number of the transaction logs which are accumulated in the master database server and are not successfully transmitted exceeds a preset value, or the transmission time of the first transaction log exceeds a preset time, the master database server transmits the first transaction log or the information of the update object corresponding to the first transaction log to a buffer area.
Optionally, the method further comprises:
and when the main database server confirms that the first transaction log or the information of the updated object corresponding to the first transaction log is transmitted to the buffer area, completing the transaction submitting operation and informing the client that the transaction is successfully submitted.
Optionally, after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further includes:
the master database server proceeds to send the first transaction log to the slave database server.
Optionally, after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further includes:
after the master database server confirms that the first transaction log has been sent to the slave database server, the master database server sends an indication message to the buffer, where the indication message is used to indicate the buffer to delete the first transaction log.
Optionally, after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further includes:
when master-slave switching occurs between the master database server and the slave database server, the slave database server takes out the first transaction log from the buffer area and plays back the first transaction log so as to synchronize data between the slave database server and the master database server, and the external service is started after the playback is completed.
Optionally, after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further includes:
when master-slave switching occurs between the master database server and the slave database server, the slave database server extracts information of an update object corresponding to the first transaction log from the buffer area, wherein the information of the update object is specifically master key or page number information, and locks a corresponding master key or page according to the master key or page number information to start providing service to the outside.
Optionally, the method further comprises:
when the database transaction received from the database server accesses the locked data, waiting; and releasing the locked data and continuing the database transaction after the first transaction log is played back until the first transaction log is received from the database server.
Optionally, the method further comprises:
and the slave database server receives the first transaction log and plays back the first transaction log so as to enable the slave database server to synchronize data with the master database server.
In another aspect, a database system is provided, the system comprising: a master database server, a slave database server and a buffer;
the master database server is used for changing data in a database according to a service providing request when the master database server receives the service providing request of a client, writing the changing information of the database into a first transaction log and sending the first transaction log to a slave database server;
the slave database server is used for receiving the first transaction log sent by the master database server;
the master database server is further configured to transmit the first transaction log or information of an update object corresponding to the first transaction log to a buffer area when a network connection between the master database server and the slave database server is disconnected or is overtime, or a number of transaction logs accumulated in the master database server and failed to be transmitted exceeds a preset value, or a transmission time of the first transaction log exceeds a preset time;
the buffer area is used for storing the first transaction log or information of an update object corresponding to the first transaction log.
Optionally, the master database server is further configured to complete a transaction commit operation when the master database server confirms that the first transaction log or the information of the update object corresponding to the first transaction log has been transmitted to the buffer, and notify the client that the transaction commit is successful.
Optionally, the master database server is further configured to continue to send the first transaction log to the slave database server after transmitting the first transaction log or information of an update object corresponding to the first transaction log to a buffer.
Optionally, the master database server is further configured to send an indication message to the buffer after confirming that the first transaction log has been sent to the slave database server, where the indication message is used to indicate the buffer to delete the first transaction log.
Optionally, the slave database server is further configured to, after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, when master-slave switching occurs between the master database server and the slave database server, take out the first transaction log from the buffer, and play back the first transaction log, so that the slave database server and the master database server synchronize data, and the play back is completed and the external service is started.
Optionally, the slave database server is further configured to, after the master database server transmits the first transaction log or the information of the update object corresponding to the first transaction log to a buffer, when master-slave switching occurs between the master database server and the slave database server, take out the information of the update object corresponding to the first transaction log from the buffer by the slave database server, where the information of the update object is specifically master key or page number information, lock the corresponding master key or page according to the master key or page number information, and start to provide a service to the outside.
Optionally, the slave database server is further configured to wait when the database transaction received from the slave database server accesses the locked data; and releasing the locked data and continuing the database transaction after the first transaction log is played back until the first transaction log is received from the database server.
Optionally, the slave database server is further configured to receive the first transaction log, and play back the first transaction log, so that the slave database server synchronizes data with the master database server.
The application provides a service providing method of a database, which is characterized in that a buffer area is additionally arranged on the basis of a master-slave architecture, and when a backup library cannot receive logs temporarily, the master library sends the logs to the buffer area, so that the logs can be ensured not to be lost. Moreover, after the main database server confirms that the first transaction log or the information of the updated object corresponding to the first transaction log is transmitted to the buffer area, the transaction submitting operation is completed, the client is informed that the transaction is successfully submitted, so that the log can be transmitted as soon as possible, the transaction submitting is completed, the performance of the main database is effectively improved, and meanwhile, the usability of the whole system is not influenced.
Drawings
FIG. 1 is a diagram of a database system architecture according to an embodiment of the present application;
fig. 2 is a signal flow diagram of a service providing method for a database according to a second embodiment of the present application;
fig. 3 is a diagram of a database system architecture according to a third embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
For the purpose of facilitating understanding of the embodiments of the present application, the following description will be made in terms of specific embodiments with reference to the accompanying drawings, which are not intended to limit the embodiments of the present application.
Fig. 1 is a diagram of an architecture of a database system according to an embodiment of the present application, the system is further provided with a buffer area on the basis of a master-slave architecture, and referring to fig. 1, the database system specifically includes a master database server, a slave database server, and a buffer area. Based on the system architecture shown in fig. 1, the present application provides a method for providing a database service, in which when a slave database server, i.e., a standby database, cannot receive a log temporarily, a master database server, i.e., a master database, sends the log to a buffer to transfer the log as soon as possible, thereby completing the transaction submission, effectively improving the performance of the master database, and at the same time, not affecting the availability of the whole system.
Fig. 2 is a signal flow diagram of a service providing method for a database according to a second embodiment of the present application, where the method is based on the database system architecture shown in fig. 1, and referring to fig. 2, the method includes:
in step 201, a primary database server receives a service providing request of a client.
When a user needs to access a database, connection is established between the client and a main database server, and the main database server provides service for the user through a service process after receiving a service providing request of the client.
In step 202, the master database server changes the data in the database according to the service providing request, and writes the change information of the database into the first transaction log.
In the embodiment of the application, the execution sequence of the operation of changing data and the operation of writing in the log is not limited, the log can be written after the data is changed, the data can be changed after the log is written, and the log and the data can be written simultaneously.
The master database server sends the first transaction log to the slave database server, step 203.
Wherein, the log writing and transmitting module may perform the operations of writing and transmitting the log by the log writing and transmitting module by setting the log writing and transmitting module in the master database server.
And step 204, after receiving the first transaction log from the database server, playing back the first transaction log so as to synchronize data between the slave database server and the master database server.
Specifically, the first transaction log may be played back through a log playback process.
In step 205, when the master database server determines that the log cannot be timely transmitted to the slave database server, that is, when the master database server cannot normally perform step 204, the master database server transmits the first transaction log or information of the update object corresponding to the first transaction log to the buffer.
In the embodiment of the present application, the master database server may determine, but is not limited to, that the log cannot be timely transmitted to the slave database server under the following conditions: when a network connection between the master database server and the slave database server is disconnected or timed out, or the number of the transaction logs accumulated in the master database server that are not successfully transmitted exceeds a preset value, or the transmission time of the first transaction log exceeds a preset time.
The reason for the disconnection or timeout of the network connection may be due to a network bandwidth bottleneck or a performance bottleneck of the backup repository.
The information of the update object corresponding to the first transaction log may be a primary key value or a page number.
The buffer provides in particular a message queue or a buffering service for buffering.
And step 206, when the master database server confirms that the first transaction log has been sent to the slave database server, or when the master database server confirms that the slave database server has completed playing back the first transaction log, or when the master database server confirms that the first transaction log or the information of the update object corresponding to the first transaction log has been transmitted to the buffer, completing the transaction submitting operation and notifying the client that the transaction is successfully submitted.
The application provides a service providing method of a database, which enlarges the range of a master database server completing transaction submitting operation, not only can complete the transaction submitting operation when the master database server confirms that a first transaction log is sent to a slave database server, or after the master database server confirms that the slave database server finishes replaying the first transaction log, but also when the slave database server, namely a standby database, can not receive the log temporarily, the master database server, namely the master database, sends the log or information of an updating object corresponding to the log to a buffer area, thereby completing the transaction submitting, effectively improving the performance of the master database, and simultaneously not influencing the availability of the whole system.
In a master-slave architecture of a database system, two servers, namely a master database server and a slave database server, are arranged mainly for the purpose of performing master-slave switching when the master library is unavailable, and the slave library provides services for users.
In a specific embodiment of the present application, when a master-slave switch occurs between the master database server and the slave database server, the first transaction log is taken out from the buffer by the slave database server, and the first transaction log is played back, so that the slave database server and the master database server synchronize data, and the external service is provided after the playback is completed.
In another specific embodiment of the present application, when a master-slave switch occurs between the master database server and the slave database server, the slave database server extracts information of an update object corresponding to the first transaction log from the buffer, where the information of the update object is specifically the information of a master key or a page number, and locks the corresponding master key or page according to the information of the master key or the page number to start providing services to the outside.
Optionally, when a database transaction received from the database server accesses the locked data, it waits; and releasing the locked data after the first transaction log is received from the database server and played back, and continuing the database transaction from the database server.
In addition, another approach may be taken, where a database transaction received from a database server accesses locked data, and waits; and continuing the database transaction by the master database server until the master database server is recovered.
Optionally, after the master database server transmits the first transaction log or information of the update object corresponding to the first transaction log to the buffer, the master database server continues to transmit the first transaction log to the slave database server.
Alternatively, after the master database server confirms that the first transaction log has been transmitted to the slave database server, the master database server transmits an indication message to the buffer, the indication message being for instructing the buffer to delete the first transaction log.
The scheme provided by the embodiment of the application has the availability equivalent to a one-master-two-slave scheme, wherein the one-master-two-slave scheme is a service providing method of a database based on a system architecture of a master database server and two slave database servers. In addition, in the embodiment of the application, as the buffer area only needs to provide the space for storing the logs when the transmission of the main log and the standby log is abnormal, and the buffer area can discard the logs after the transmission of the main log and the standby log is recovered to be normal, the requirement on the storage space of the buffer area is low, the practicability is high, and the cost is low; and as a global service, one buffer can serve a plurality of database systems, so that compared with a master-slave scheme, the scheme reduces the requirement on hardware and correspondingly greatly reduces the cost.
Fig. 3 is an architecture diagram of a database system provided in a third embodiment of the present application, where the system is configured to execute a service providing method for a database provided in the third embodiment of the present application, and referring to fig. 3, the system includes: a master database server 301, a slave database server 302, and a buffer 303;
the master database server 301 is configured to, when the master database server 301 receives a service providing request from a client, change data in a database according to the service providing request, write change information of the database into a first transaction log, and send the first transaction log to the slave database server 302;
the slave database server 302 is configured to receive the first transaction log sent by the master database server 301;
the master database server 301 is further configured to transmit the first transaction log or information of an update object corresponding to the first transaction log to a buffer 303 when a network connection between the master database server 301 and the slave database server 302 is disconnected or is over time, or the number of transaction logs that are accumulated in the master database server 301 and are not successfully transmitted exceeds a preset value, or the transmission time of the first transaction log exceeds a preset time;
the buffer 303 is configured to store the first transaction log or information of an update object corresponding to the first transaction log.
Optionally, the master database server 301 is further configured to complete a transaction commit operation when the master database server 301 confirms that the first transaction log or the information of the update object corresponding to the first transaction log has been transmitted to the buffer 303, and notify the client that the transaction commit is successful.
Optionally, the master database server 301 is further configured to continue to send the first transaction log to the slave database server 302 after transmitting the first transaction log or information of an update object corresponding to the first transaction log to the buffer 303.
Optionally, the master database server 301 is further configured to send an indication message to the buffer 303 after confirming that the first transaction log has been sent to the slave database server 302, where the indication message is used to indicate that the buffer 303 deletes the first transaction log.
Optionally, the slave database server 302 is further configured to, after the master database server 301 transmits the first transaction log or information of an update object corresponding to the first transaction log to the buffer 303, when master-slave switching occurs between the master database server 301 and the slave database server 302, take out the first transaction log from the buffer 303, play back the first transaction log, so that the slave database server 302 synchronizes data with the master database server 301, and start to provide a service to the outside after the playback is completed.
Optionally, the slave database server 302 is further configured to, after the master database server 301 transmits the first transaction log or the information of the update object corresponding to the first transaction log to the buffer 303, when master-slave switching occurs between the master database server 301 and the slave database server 302, the slave database server 302 extracts the information of the update object corresponding to the first transaction log from the buffer 303, where the information of the update object is specifically the information of a master key or a page number, and locks the corresponding master key or page according to the information of the master key or the page number, so as to start to provide a service to the outside.
Optionally, the slave database server 302 is further configured to wait when the database transaction received from the slave database server 302 accesses the locked data; until the first transaction log is received from the database server 302, the locked data is released after the first transaction log is played back, and the database transaction is resumed.
Optionally, the slave database server 302 is further configured to receive the first transaction log, and play back the first transaction log, so that the slave database server 302 synchronizes data with the master database server 301.
Those of skill would further appreciate that the various illustrative objects and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, a software module executed by a processor, or a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The above-mentioned embodiments, objects, technical solutions and advantages of the present application are described in further detail, it should be understood that the above-mentioned embodiments are merely exemplary embodiments of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made within the spirit and principle of the present application should be included in the scope of the present application.
Claims (16)
1. A method for providing a service to a database, the method comprising:
when a master database server receives a service providing request of a client, changing data in a database according to the service providing request, writing the changing information of the database into a first transaction log, and sending the first transaction log to a slave database server;
when a network connection between the master database server and the slave database server is disconnected or is overtime, or the number of transaction logs which are accumulated in the master database server and are not successfully transmitted exceeds a preset value, or the transmission time of the first transaction log exceeds a preset time, the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer area;
and when the main database server confirms that the first transaction log or the information of the updated object corresponding to the first transaction log is transmitted to the buffer area, completing the transaction submitting operation.
2. The method of claim 1, wherein after completion of the transaction commit operation, the method further comprises:
and informing the client that the transaction is successfully submitted.
3. The method of claim 2, wherein after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further comprises:
the master database server proceeds to send the first transaction log to the slave database server.
4. The method of claim 3, wherein after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further comprises:
after the master database server confirms that the first transaction log has been sent to the slave database server, the master database server sends an indication message to the buffer, where the indication message is used to indicate the buffer to delete the first transaction log.
5. The method of claim 1, wherein after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further comprises:
when master-slave switching occurs between the master database server and the slave database server, the slave database server takes out the first transaction log from the buffer area and plays back the first transaction log so as to synchronize data between the slave database server and the master database server, and the external service is started after the playback is completed.
6. The method of claim 1, wherein after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, the method further comprises:
when master-slave switching occurs between the master database server and the slave database server, the slave database server extracts information of an update object corresponding to the first transaction log from the buffer area, wherein the information of the update object is specifically master key or page number information, and locks a corresponding master key or page according to the master key or page number information to start providing service to the outside.
7. The method of claim 6, wherein the method further comprises:
when the database transaction received from the database server accesses the locked data, waiting; and releasing the locked data and continuing the database transaction after the first transaction log is played back until the first transaction log is received from the database server.
8. The method of any of claims 1 to 7, further comprising:
and the slave database server receives the first transaction log and plays back the first transaction log so as to enable the slave database server to synchronize data with the master database server.
9. A database system, the system comprising: a master database server, a slave database server and a buffer;
the master database server is used for changing data in a database according to a service providing request when the master database server receives the service providing request of a client, writing the changing information of the database into a first transaction log and sending the first transaction log to a slave database server;
the slave database server is used for receiving the first transaction log sent by the master database server;
the master database server is further configured to transmit the first transaction log or information of an update object corresponding to the first transaction log to a buffer area when a network connection between the master database server and the slave database server is disconnected or is overtime, or a number of transaction logs accumulated in the master database server and failed to be transmitted exceeds a preset value, or a transmission time of the first transaction log exceeds a preset time;
the buffer area is used for storing the first transaction log or information of an update object corresponding to the first transaction log;
and the master database server is further configured to complete a transaction submitting operation when the master database server confirms that the first transaction log or the information of the update object corresponding to the first transaction log has been transmitted to the buffer.
10. The system of claim 9, wherein:
the main database server is further used for informing the client that the transaction is successfully submitted after the transaction submitting operation is completed.
11. The system of claim 10, wherein the master database server is further configured to continue to transmit the first transaction log to the slave database server after transmitting the first transaction log or information of an update object corresponding to the first transaction log to a buffer.
12. The system of claim 11, wherein the master database server is further configured to send an indication message to the buffer after confirming that the first transaction log has been sent to the slave database server, the indication message indicating to the buffer to delete the first transaction log.
13. The system of claim 9, wherein the slave database server is further configured to, after the master database server transmits the first transaction log or information of an update object corresponding to the first transaction log to a buffer, when a master-slave switch occurs between the master database server and the slave database server, retrieve the first transaction log from the buffer, and play back the first transaction log, so that the slave database server synchronizes data with the master database server, and the playback is completed to start providing a service to the outside.
14. The system of claim 9, wherein the slave database server is further configured to, after the master database server transmits the first transaction log or information of the update object corresponding to the first transaction log to a buffer, when a master-slave switch occurs between the master database server and the slave database server, retrieve, by the slave database server, the information of the update object corresponding to the first transaction log from the buffer, where the information of the update object is specifically master key or page number information, and lock a corresponding master key or page according to the master key or page number information to start providing external services.
15. The system of claim 14, wherein the slave database server is further configured to wait when the database transaction received from the database server accesses the locked data; and releasing the locked data and continuing the database transaction after the first transaction log is played back until the first transaction log is received from the database server.
16. The system of any one of claims 9 to 15, wherein:
the slave database server is further configured to receive the first transaction log and play back the first transaction log, so that the slave database server and the master database server synchronize data.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510955708.7A CN106897288B (en) | 2015-12-18 | 2015-12-18 | Service providing method and system for database |
| PCT/CN2016/108991 WO2017101731A1 (en) | 2015-12-18 | 2016-12-08 | Service providing method and system for database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510955708.7A CN106897288B (en) | 2015-12-18 | 2015-12-18 | Service providing method and system for database |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106897288A CN106897288A (en) | 2017-06-27 |
| CN106897288B true CN106897288B (en) | 2021-01-08 |
Family
ID=59055824
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510955708.7A Active CN106897288B (en) | 2015-12-18 | 2015-12-18 | Service providing method and system for database |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106897288B (en) |
| WO (1) | WO2017101731A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110019502B (en) * | 2017-08-29 | 2023-03-21 | 阿里巴巴集团控股有限公司 | Synchronization method between primary database and backup database, database system and device |
| CN110955556B (en) * | 2018-09-27 | 2023-05-02 | 阿里云计算有限公司 | Database recovery method and device, storage medium and database system |
| CN111124757A (en) * | 2019-12-16 | 2020-05-08 | 上海热璞网络科技有限公司 | Data node heartbeat detection algorithm of distributed transaction database |
| CN112416654B (en) * | 2020-11-26 | 2024-04-09 | 上海达梦数据库有限公司 | Database log replay method, device, equipment and storage medium |
| CN113377582B (en) * | 2021-08-16 | 2021-11-05 | 北京易鲸捷信息技术有限公司 | Distributed database disaster tolerance method based on log pushing |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101681383A (en) * | 2007-05-21 | 2010-03-24 | Nhn株式会社 | Data replication method and system for database management system |
| CN101706811A (en) * | 2009-11-24 | 2010-05-12 | 中国科学院软件研究所 | Transaction commit method of distributed database system |
| CN101876924A (en) * | 2009-04-30 | 2010-11-03 | 升东网络科技发展(上海)有限公司 | Database fault automatic detection and transfer method |
| CN102629268A (en) * | 2012-03-09 | 2012-08-08 | 华为技术有限公司 | Data synchronization method, system and date access device |
| CN103546579A (en) * | 2013-11-07 | 2014-01-29 | 陈靓 | Method for improving availability of distributed storage system through data logs |
| CN104468399A (en) * | 2014-12-08 | 2015-03-25 | 北京奇虎科技有限公司 | Data transmission method and device and server |
| CN104601354A (en) * | 2013-10-31 | 2015-05-06 | 深圳市腾讯计算机系统有限公司 | Business log storage method, device and system |
| CN104967658B (en) * | 2015-05-08 | 2018-11-30 | 成都品果科技有限公司 | A kind of method of data synchronization on multi-terminal equipment |
Family Cites Families (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100896177B1 (en) * | 2004-11-17 | 2009-05-12 | 삼성전자주식회사 | High speed flip-flop |
| KR100918398B1 (en) * | 2007-12-13 | 2009-09-21 | 한국전자통신연구원 | Apparatus and method for processing VLAN Tag frame |
| US9092567B2 (en) * | 2012-06-29 | 2015-07-28 | Freescale Semiconductor, Inc. | Systems and methods for analyzing transactions in a computer system |
| CN103580891A (en) * | 2012-07-27 | 2014-02-12 | 腾讯科技（深圳）有限公司 | Data synchronization method and system and servers |
| CN103580906B (en) * | 2012-08-09 | 2018-02-27 | 腾讯科技（深圳）有限公司 | A kind of method of data backup, system and server |
| US9417974B2 (en) * | 2013-03-28 | 2016-08-16 | Microsoft Technology Licensing, Llc. | Transaction processing for database in persistent system |
| CN103475718A (en) * | 2013-09-11 | 2013-12-25 | 北京京东尚科信息技术有限公司 | Data caching method and system |
| US9558229B2 (en) * | 2013-11-26 | 2017-01-31 | Sap Se | Transaction private log buffering for high performance of transaction processing |
| EP2889812A1 (en) * | 2013-12-24 | 2015-07-01 | Pathway IP SARL | Room access control system |
| US10817500B2 (en) * | 2014-03-13 | 2020-10-27 | Sybase, Inc. | Reduce log contention by batching log record transfers to the log |
| CN105162560A (en) * | 2015-08-24 | 2015-12-16 | 浪潮(北京)电子信息产业有限公司 | Data processing method and system |
-
2015
- 2015-12-18 CN CN201510955708.7A patent/CN106897288B/en active Active
-
2016
- 2016-12-08 WO PCT/CN2016/108991 patent/WO2017101731A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101681383A (en) * | 2007-05-21 | 2010-03-24 | Nhn株式会社 | Data replication method and system for database management system |
| CN101876924A (en) * | 2009-04-30 | 2010-11-03 | 升东网络科技发展(上海)有限公司 | Database fault automatic detection and transfer method |
| CN101706811A (en) * | 2009-11-24 | 2010-05-12 | 中国科学院软件研究所 | Transaction commit method of distributed database system |
| CN102629268A (en) * | 2012-03-09 | 2012-08-08 | 华为技术有限公司 | Data synchronization method, system and date access device |
| CN104601354A (en) * | 2013-10-31 | 2015-05-06 | 深圳市腾讯计算机系统有限公司 | Business log storage method, device and system |
| CN103546579A (en) * | 2013-11-07 | 2014-01-29 | 陈靓 | Method for improving availability of distributed storage system through data logs |
| CN104468399A (en) * | 2014-12-08 | 2015-03-25 | 北京奇虎科技有限公司 | Data transmission method and device and server |
| CN104967658B (en) * | 2015-05-08 | 2018-11-30 | 成都品果科技有限公司 | A kind of method of data synchronization on multi-terminal equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2017101731A1 (en) | 2017-06-22 |
| CN106897288A (en) | 2017-06-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106897288B (en) | Service providing method and system for database | |
| JP6602369B2 (en) | Secure data access after memory failure | |
| US8335771B1 (en) | Storage array snapshots for logged access replication in a continuous data protection system | |
| US8464101B1 (en) | CAS command network replication | |
| US20150213100A1 (en) | Data synchronization method and system | |
| CN103530362B (en) | A kind of computer data reading/writing method for many copies distributed system | |
| US20070078911A1 (en) | Replicating data across the nodes in a cluster environment | |
| CN110597910A (en) | Remote data synchronization method, device and system | |
| CN104937904B (en) | Method, system and computer storage media for unloading | |
| US20110137874A1 (en) | Methods to Minimize Communication in a Cluster Database System | |
| US11620087B2 (en) | Implicit leader election in a distributed storage network | |
| CN113268472B (en) | Distributed data storage system and method | |
| CN106873902B (en) | File storage system, data scheduling method and data node | |
| WO2018157605A1 (en) | Message transmission method and device in cluster file system | |
| EP2569921A1 (en) | System and method for providing reliable storage | |
| US11693844B2 (en) | Processing delete requests based on change feed of updates | |
| US20200387412A1 (en) | Method To Manage Database | |
| US9026849B2 (en) | System and method for providing reliable storage | |
| CN105511808A (en) | Data operation method, system and related device | |
| CN109992447A (en) | Data copy method, device and storage medium | |
| US20120191645A1 (en) | Information processing apparatus and database system | |
| US20160179408A1 (en) | Information processing system, server device, information processing method, and computer program product | |
| CN115698955A (en) | Fault tolerance of transaction images | |
| CN102368268B (en) | Method for achieving consistency of pieces of metadata | |
| TWI735518B (en) | Service provision method and system of database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |