Slave consistency in a synchronous replication environment

• US 8,694,733 B2
• Filed: 02/17/2012
• Issued: 04/08/2014
• Est. Priority Date: 01/03/2011
• Status: Expired due to Fees

• Current Assignee: SanDisk Technologies LLC (Western Digital Corporation)
• Original Assignee: SanDisk Enterprise IP LLC (Western Digital Corporation)
• Inventors: Krishnan, Manavalan, Dinker, Darpan, George, Johann
• Primary Examiner(s): NGUYEN, HIEP T
• Application Number:
  US13/399,982
• Publication Number:
  US 20130151467A1
• Time in Patent Office: 781 Days
• US Class Current: 711/133
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

Approaches for replicating data in a distributed transactional system. At a first node of a cluster, a per-transaction write set, comprising a plurality of write operations, is committed against a first MySQL database. One or more per-transaction write sets are replicated from the first node to a second node. Upon receiving a read query, the second node parses the read query to identify a read set, calculates a write set conflict window for the read query, and upon determining that the read set conflicts with one or more write sets in the write set conflict window, waits to process the read query until all conflicting write sets are committed. However, upon determining that the read set does not conflict any write sets in the write set conflict window, the read query is processed without first committing any write transactions in the write set conflict window for the read query.

Claims

1. A method for replicating data in a distributed transactional system, comprising:

at a first node of a cluster, committing a per-transaction write set that comprises a plurality of write operations that are performed against a first database maintained by the first node;

replicating one or more per-transaction write sets from the first node to a second node of the cluster; and

upon receiving a read query at the second node, the second node performing;

parsing the read query to identify a read set,

calculating a write set conflict window for the read query, and

upon determining that the read set conflicts with one or more write sets in the write set conflict window, waiting to process the read query until all write sets in the write set conflict window that conflict with the read query are committed.

2. The method of claim 1, wherein replicating is performed synchronously such that a write transaction is not committed at the first node until the first node receives acknowledgement, from the second node, that the write transaction is received at the second node.

3. The method of claim 1, wherein the first node operates as a master and the second node operates as a slave.

4. The method of claim 1, wherein the one or more per-transaction write sets, once received at the second node, are stored in a write-set queue prior to being processed by the second node.

5. The method of claim 1, further comprising:

upon the second node determining that the read set does not conflict with any write sets in the write set conflict window for the read query, processing the read query without first committing any write transactions in the write set conflict window for the read query.

6. The method of claim 1, further comprising:

replicating the one or more per-transaction write sets from the first node to one or more other nodes of the cluster besides the second node.

7. A non-transitory machine readable storage medium storing one or more sequences of instructions for replicating data in a distributed transactional system, wherein execution of the one or more sequences of instructions causes:

at a first node of a cluster, committing a per-transaction write set that comprises a plurality of write operations that are performed against a first database maintained by the first node;

replicating one or more per-transaction write sets from the first node to a second node of the cluster; and

upon receiving a read query at the second node, the second node performing;

parsing the read query to identify a read set,

calculating a write set conflict window for the read query, and

upon determining that the read set conflicts with one or more write sets in the write set conflict window, waiting to process the read query until all write sets in the write set conflict window that conflict with the read query are committed.

8. The non-transitory machine readable storage medium of claim 7, wherein replicating is performed synchronously such that a write transaction is not committed at the first node until the first node receives acknowledgement, from the second node, that the write transaction is received at the second node.

9. The non-transitory machine readable storage medium of claim 7, wherein the first node operates as a master and the second node operates as a slave.

10. The non-transitory machine readable storage medium of claim 7, wherein the one or more per-transaction write sets, once received at the second node, are stored in a write-set queue prior to being processed by the second node.

11. The non-transitory machine readable storage medium of claim 7, wherein execution of the one or more sequences of instructions further causes:

upon the second node determining that the read set does not conflict with any write sets in the write set conflict window for the read query, processing the read query without first committing any write transactions in the write set conflict window for the read query.

12. The non-transitory machine readable storage medium of claim 7, wherein execution of the one or more sequences of instructions further causes replicating the one or more per-transaction write sets from the first node to one or more other nodes of the cluster besides the second node.

13. A system for replicating data in a distributed transactional system, comprising:

one or more processors; and

a machine readable storage medium storing one or more sequences of instructions, which when executed by the one or more processors, cause;

at a first node of a cluster, committing a per-transaction write set that comprises a plurality of write operations that are performed against a first database maintained by the first node;

replicating one or more per-transaction write sets from the first node to a second node of the cluster; and

upon receiving a read query at the second node, the second node performing;

parsing the read query to identify a read set,

calculating a write set conflict window for the read query, and

upon determining that the read set conflicts with one or more write sets in the write set conflict window, waiting to process the read query until all write sets in the write set conflict window that conflict with the read query are committed.

14. The system of claim 13, wherein replicating is performed synchronously such that a write transaction is not committed at the first node until the first node receives acknowledgement, from the second node, that the write transaction is received at the second node.

15. The system of claim 13, wherein the first node operates as a master and the second node operates as a slave.

16. The system of claim 13, wherein the one or more per-transaction write sets, once received at the second node, are, stored in a write-set queue prior to being processed by the second node.

17. The system of claim 13, wherein execution of the one or more sequences of instructions further causes:

upon the second node determining that the read set does not conflict with any write sets in the write set conflict window for the read query, processing the read query without first committing any write transactions in the write set conflict window for the read query.

18. The system of claim 13, wherein execution of the one or more sequences of instructions further causes replicating the one or more per-transaction write sets from the first node to one or more other nodes of the cluster besides the second node.