US 9,002,793 B1Granted

Database replication

AssigneeGoogle Inc.

InventorsKenneth M Ashcraft, Jean-Michel Leon, Vishal Kasera, Amit Agarwal

Life of this patent

Estimating the term…

Loading patent…

Abstract

A write request is received at a database server from a client application for writing data to persistent data storage. In response to receiving the write request, the database server selects a set of multiple replication servers. The data is sent from the database server to the selected set of multiple replication servers for writing to the persistent data storage. Confirmation is received at the database server from replication servers in the selected set of multiple replication servers. In response to receiving confirmation from the replication servers in the selected set of multiple replication servers, the database server sends to the client application information indicating success of the write request.

Claims20

Dependent claims

A method comprising:

receiving, at a database server, a write request from a client application for writing data to persistent data storage;
in response to receiving the write request, selecting, by the database server, a set of multiple replication servers;
sending the data from the database server to the selected set of multiple replication servers for writing to the persistent data storage;
receiving, at the database server, confirmation from less than all of the replication servers in the selected set of multiple replication servers;
and
in response to receiving confirmation from the replication servers in the selected set of multiple replication servers, selecting, by the database server, one or more additional replication servers as replacement for the replication servers from which confirmation is not received;
and
sending the data from the database server to the additional replication servers.

5 more elements

A computer program product, suitably embodied in a non-transitory machine-readable medium and including instructions executable by a processor, the instructions configured to cause the processor to perform operations comprising:

receiving, at a database server, a write request from a client application for writing data to persistent data storage;
in response to receiving the write request, selecting, by the database server, a set of multiple replication servers;
sending the data from the database server to the selected set of multiple replication servers for writing to the persistent data storage;
receiving, at the database server, confirmation from less than all of the replication servers in the selected set of multiple replication servers;
and
in response to receiving confirmation from the replication servers in the selected set of multiple replication servers, selecting, by the database server, one or more additional replication servers as replacement for the replication servers from which confirmation is not received;
and
sending the data from the database server to the additional replication servers.

5 more elements

Dependencies are inferred from the claim text.

Facts

Application: 13/645,989Filed 5 Oct 2012 · us provisional application
Priority: 5 Oct 2011
Granted: 7 Apr 2015
Term ends: Not estimatedThe source records don’t support an estimate.

Classification8 codes

G06F 16/273
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system…:…
G06F 12/0806
Addressing of a memory level in which the access to the desired data or data block requires associative addressing means, e.g. caches: multiuser,…
G06F 16/215
Design, administration or maintenance of databases: improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or…
G06F 16/27
Of structured data, e.g. relational data: replication, distribution or synchronisation of data between databases or within a distributed database…