US 2019/0102410 A1Published application

Systems and methods for automating management of distributed databases

AssigneeMongoDB, Inc.

InventorsEliot Horowitz, Cailin Anne Nelson, Louisa Berger

Life of this patent

Estimating the term…

Loading patent…

Abstract

An automation system is provided to automate any administrative task in a distributed database, such that the end user can input a goal state (e.g., create database with a five node architecture) and the automation system generates and executes a plan to achieve the goal state without further user input. According to another aspect, bringing existing database systems into automated management can be as complex as designing the database itself. According to some embodiments, the automation system is configured to analyze existing database systems, capture and/or install monitoring components within the existing database, and generate execution pathways to integrate existing database systems into automation control systems. Based on the current state information, the automation system is configured to generate an installation pathway of one or more intermediate states to transition the existing system from no automation to a goal state having active automation agents distributed throughout the database.

Claims20

Dependent claims

A system for automatically integrating cloud based resources into a distributed database executing on local hardware, the system comprising:

at least one processor operatively connected to a memory;
a state component, executed by the at least one processor, configured to determine a current state for a plurality of database nodes, wherein the current state determination identifies a database instance executing on client hardware including at least one replica set having a primary node hosting a primary database instance that accepts database write operations from client systems, and at least two secondary nodes that host copies of the primary database instance that replicate logged write operations from the primary node, a database version executing on the replica set, and configuration data for at least one database instance;
a planning component, executed by the at least one processor, configured to generate an execution plan to provision an additional secondary node mirroring the primary node and the primary database;
and
an automation component, executed by the at least one processor, configured to:
provision at least one cloud resource having processor and memory based on the execution plan;
install database binary files including automation agents for a secondary node on the at least one cloud resource;
trigger synchronization between the primary node and the secondary node executing on the at least one cloud resource;
and
update configuration metadata for the database instance;
and
replicate write operations on the primary node executing on client hardware received after synchronization to the secondary node executing on the at least one cloud resource.

9 more elements

A computer implemented method for automatically integrating cloud based resources into a distributed database executing on local hardware, the method comprising:

determining, by at least one processor, a current state for a plurality of database nodes, wherein determining the current state includes identifying a database instance executing on client hardware including at least one replica set having a primary node hosting a primary database instance that accepts database write operations from client systems, and at least two secondary nodes that host copies of the primary database instance that replicate logged write operations from the primary node, a database version executing on the replica set, and configuration data for at least one database instance;
generating, by the at least one processor, an execution plan to provision an additional secondary node mirroring the primary node and the primary database;
provisioning, by the at least one processor, at least one cloud resource having processor and memory based on the execution plan;
installing, by the at least one processor, database binary files including automation agents for a secondary node on the at least one cloud resource;
triggering, by the at least one processor, synchronization between the primary node and the secondary node executing on the at least one cloud resource;
updating, by the at least one processor, configuration metadata for the database instance;
and
replicating, by the at least one processor, any write operations receive on the primary node executing on client hardware after synchronization to the secondary node executing on the at least one cloud resource.

5 more elements

Dependencies are inferred from the claim text.

Facts

Application: 16/035,370Filed 13 Jul 2018
Priority: 15 Dec 2015
Published: 4 Apr 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification6 codes

G06F 16/211
Design, administration or maintenance of databases: schema design and management
G06F 16/2228
Indexing; Data structures therefor; Storage structures: indexing structures
G06F 16/275
Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system…:…
H04L 9/0891
Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords: revocation or update of secret…

Family

Application14/969,537Continuation · filed 15 Dec 2015
Application15/654,601Continuation · filed 19 Jul 2017
Application16/035,370Continuation
US 10,031,931 B2Related patent
US 10,489,357 B2Related patent
US 2017/0169059 A1Published application
US 2017/0322954 A1Published application
US 9,881,034 B2Related patent
US 2019/0102410 A1This patent

From the US filing history. Foreign family members aren’t listed.