DEPENDENCY MANAGER FOR DATABASES

• US 20150154233A1
• Filed: 12/02/2014
• Published: 06/04/2015
• Est. Priority Date: 12/02/2013
• Status: Active Grant

• Current Assignee: Finch Computing LLC (Qbase, LLC)
• Original Assignee: Qbase, LLC
• Inventors: LIGHTNER, Scott, WECKESSER, Franz
• Granted Patent: US 9,348,573 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/2025 using centralised failover control functionality
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 16/1734 Details of monitoring file system events, e.g. by the use of hooks, filter drivers, logs
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/28 Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

The present disclosure relates to in-memory databases or search engines using a dependency manager or configuration manager for maintaining configuration in the database system. The system may include a supervisor that may request and receive data from dependency manager, where the supervisor may be linked to other components in the system. The dependency manager may be used as a container for data metadata, and software components, which may be used in the system configuration. The configuration may be developed through a dependency system, where the dependency manager may keep an entire dependency tree for all software and data in the system. Similarly, dependency manager may create a deployable package to guarantee deployment integrity and to ensure a successful execution of any suitable software and data in the system.

Claims

1. A computer-implemented method comprising:

transmitting, by a computer of a distributed computing system, to a dependency manager node a request for a machine-readable deployable package file associated with a target node, wherein the dependency manager node comprises a non-transitory machine-readable storage medium storing one or more deployable package files associated with one or more nodes of the system according to dependency tree;

transmitting, by the computer, the deployable package file to the target node in response to receiving the deployable package file from the dependency node, wherein the deployable package file associated with the target node contains a set of one or more dependency files based on the dependency tree; and

instructing, by the computer, the target node to install the set of dependencies in the deployable package onto the target node.

2. The method according to claim 1, wherein a dependency is selected from the group consisting of:

a partition, a module, a file, and data.

3. The method according to claim 1, wherein the dependency manager node fetches a dependency from one or more one dataframes and compiles the deployable package.

4. The method according to claim 1, wherein each respective dependency file in the deployable package file is determined by the dependency manager node using at least one dependency tree associated with the target node, and

5. The method according to claim 4, wherein each respective dependency file in the deployable package file is based on a comparative relationship of the dependency file with a corresponding dependency file installed on a subset of one or more nodes in a system.

6. The method according to claim 1, further comprising:

receiving, by the computer, from each of the one or more nodes of the distributed computing system a heartbeat signal indicating a status of the respective node, at a predetermined interval; and

determining, by the computer, the status of each respective node based on each respective heartbeat signal.

7. The method according to claim 6, further comprising detecting, by the computer, a failure of one or more dependencies installed on the target node according to the heartbeat signal received from the target node, wherein the computer automatically requests the deployment package responsive to detecting the failure.

8. The method according to claim 6, further comprising receiving, by the computer, from a vendor server associated with a dependency file installed on a node of the system, a prompt to update the node having the dependency file associated with the vendor server, wherein the one or more dependency files of the deployment package file contains the dependency file associated with the vendor server.

9. A computer-implemented method comprising:

determining, by a computer, a set of one or more dependency files to be installed onto a target node using a dependency tree associated with the target node responsive to receiving a request to configure the target node from a supervisor node;

fetching, by the computer, each of the dependency files of the set of one or more dependency files from at least one dataframe comprising non-transitory machine-readable storage medium storing one or more dependency files;

generating, by the computer, a deployable package file comprising the set of one or more dependency files; and

transmitting, by the computer, the deployable package file to the supervisor node.

10. The method according to claim 9, further comprising updating, by the computer, the dependency tree associated with the target node upon receiving a request to update the dependency from a third-party dependency source.

11. The method according to claim 10, further comprising:

detecting, by the computer, an update to the dependency associated with an updated dependency tree; and

automatically transmitting, by the computer, an updating deployment package comprising the updated dependency to each node having the dependency that was updated, wherein the updating deployment package for each node is based on the updated dependency tree.

12. A database management system comprising:

one or more nodes comprising a non-transitory machine-readable storage memory storing one or more dependency files, and a processor monitoring a status of the one or more dependency files, wherein each respective dependency file is a component of the node having a comparative relationship with a corresponding component installed on a second node;

one or more supervisor nodes comprising a processor monitoring a status for each of the one or more nodes and configured to transmit a deployable package comprising a set of dependencies files to each of the nodes based on the status of each respective node; and

one or more dependency manager nodes comprising a non-transitory machine-readable storage medium storing one or more dependency tree files associated with the one or more nodes, and a processor configured to compile a deployable package file in accordance with a dependency tree associated with a node, wherein the deployable package file comprises a set of one or more dependencies files stored on at least one data frame, and wherein the dependency manager node determines a dependency to include in the deployable package based on a dependency tree associated with a node targeted to receive the deployable package.

13. The system according to claim 12, further comprising an external dataframe comprising a non-transitory machine-readable storage medium storing one or more machine-readable update files corresponding to one or more dependency files install updates for a dependency generated by the third-party;

and

a processor configured to transmit a request to a supervisor node to update a set of one or more nodes having the dependency of the third-party dependency source,

wherein a dependency manager node compiles an update deployment package comprising the one or more dependency updates received from the data frame of the third-party dependency source.

14. The system according to claim 12, further comprising a new node comprising a processor executing a node manager module that transmits a new node status to a supervisor node and receives one or more deployment packages according to a dependency tree associated with the new node.

15. The system according to claim 12, wherein the dependency manager node updates a dependency tree associated with a node when a request to update the dependency tree is received from a supervisor node,

16. The system according to claim 12, wherein a dependency is selected from the group consisting of:

a partition, a module, a file, and data.