US 2018/0025066 A1 · ZERO DOWNTIME DATABASE UPDATES WITH DATABASE CONFIGURATION CHANGES

Abstract

Technologies are described for performing database updates in a database environment where the database remains accessible during the updates. For example, a number of database clients may utilize a database environment for running queries or performing transactions. When an update to the database environment needs to be performed (e.g., a change to the database schema), instead of taking the database offline or queueing requests, the database can remain accessible to the database clients throughout the update process. The update process can include switching database connections between a first copy of the database and a second copy of the database that are being replicated. Technologies are also described for performing updates to application code used to interact with the database environment (e.g., alone or in combination with database system updates).

Claims20

Dependent claims

A method for performing zero downtime database updates in a database environment, the method comprising:

directing database connections from server applications to a first copy of a database, wherein the first copy of the database is being replicated to a second copy of the database, and wherein the second copy of the database is in a read-only mode;
stopping replication from the first copy of the database to the second copy of the database;
performing database system changes to the second copy of the database, the database system changes comprising database schema changes for the second copy of the database;
after performing the database system changes, resuming replication from the first copy of the database to the second copy of the database;
switching the database connections from the server applications to the second copy of the database;
and
stopping replication form the first copy of the database to the second copy of the database, and starting replication from the second copy of the database to the first copy of the database;
wherein the database remains accessible throughout the zero downtime database update.

5 more elements

A server environment comprising:

a first computer server running a master copy of a database;
a second computer server running a slave copy of the database;
the server environment configured to perform operations for zero downtime database updates, the operations comprising:
directing database connections comprising write operations from server applications to the master copy of the database, wherein the master copy of the database is being replicated to the slave copy of the database, wherein the slave copy of the database is in a read-only mode, and wherein the server applications are running a current code version;
deploying a new code version of the server applications, wherein the new code version is inactive;
stopping replication from the master copy of the database to the slave copy of the database;
performing database system changes to the slave copy of the database, the database system changes comprising database schema changes for the slave copy of the database;
after performing the database system changes, resuming replication from the master copy of the database to the slave copy of the database;
once the master and slave copies are in sync, switching the copies of the database so that the slave copy of the database becomes a new master and the master copy of the database becomes a new slave, the switching comprising directing database connections with write operations to the new master;
wherein the database remains accessible throughout the zero downtime database update.

7 more elements

A method for performing zero downtime database updates in a database environment, the method comprising:

directing database connections, for write operations, from server applications to a first copy of a database, wherein the first copy of the database is being replicated to a second copy of the database, wherein the second copy of the database is in a read-only mode, and wherein the server applications are running a current code version;
maintaining a first set of entries in a memory cache for database records returned in the database connections when the server applications are running the current code version, the first set of entries associated with the current code version;
deploying a new code version of the server applications, wherein the new code version is inactive;
stopping replication from the first copy of the database to the second copy of the database;
performing database system changes to the second copy of the database, the database system changes comprising database schema changes for the second copy of the database;
after performing the database system changes, resuming replication from the first copy of the database to the second copy of the database;
switching the database connections, for write operations, from the server applications to the second copy of the database;
stopping replication form the first copy of the database to the second copy of the database, and starting replication from the second copy of the database to the first copy of the database;
and
maintaining a second set of entries in the memory cache for database records returned in the database connections when the server applications are running the new code version, the second set of entries associated with the new code version;
wherein the database remains accessible throughout the zero downtime database update.

8 more elements

Dependencies are inferred from the claim text.

Zero downtime database updates with database configuration changes

Life of this patent

Zero downtime database updates with database configuration changes

Life of this patent

Abstract

Claims20