US 11,379,463 B1 · Atomic enforcement of cross-page data constraints in decoupled multi-writer databases

Abstract

Systems and methods are disclosed to implement, in a database system, a database engine node that generates write tracking transactions to atomically enforce cross-page constraints for write operations. In embodiments, the database system may include multiple database engine nodes that optimistically perform page writes without checking for potential conflicts at a shared storage system. The storage system is configured to detect and report conflicting writes on the same page. To cause the storage system to report cross-page conflicts for a write, the database engine node creates a transaction that includes the write and a write tracker (WT) operation for a tracked page. The WT operation will cause the storage system to report any conflicting writes to the tracked page before the actual write is accepted by the storage system. If a reported conflict is not favorably resolved, the database engine node will abort the entire transaction, including the actual write.

Claims20

Dependent claims

A system, comprising:

one or more hardware processors with associated memory that implement a plurality of database engine nodes, configured to:
send writes to pages of a database to a storage service that stores the pages;
one or more hardware processors with associated memory that implement the storage service, configured to:
report conflicts detected between writes to individual ones of the pages received from different database engine nodes;
wherein at least one of the plurality of database engine nodes is configured to:
for a write to a first page of the database:
determine that the write requires a second page of the database to remain unchanged until the write to the first page completes;
initiate a transaction to perform the write that:
sends the write to the first page of the database to the storage service;
and
sends a second write to the second page of the database to the storage service, wherein the second write does not modify the second page but causes the storage service to report a conflict responsive to the at least one of the plurality of database engine nodes detecting another write to the second page.

8 more elements

One or more non-transitory computer-accessible storage media storing program instructions that when executed on or across one or more processors implements one of a plurality of database engine nodes in a database system and cause the one of the plurality of database engine nodes to:

send writes to a storage system that stores data of a database, wherein the storage system is configured to report conflicts detected between writes received from the plurality of database engine nodes;
determine that a write to a first location of the database requires a second location of the database to remain unchanged until the write to the first location completes;
initiate a transaction to perform the write to:
send the write to the first location of the database to the storage system;
and
send a second write to the second location of the database to the storage system, wherein the second write does not modify the second location but causes the storage system to report a conflict responsive to the one of the plurality of database engine nodes detecting another write to the second location.

3 more elements

Dependencies are inferred from the claim text.

Atomic enforcement of cross-page data constraints in decoupled multi-writer databases

Life of this patent

Atomic enforcement of cross-page data constraints in decoupled multi-writer databases

Life of this patent

Abstract

Claims20