Cluster instance management system

US10361928B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10361928-B2
Application numberUS-201715682397-A
CountryUS
Kind codeB2
Filing dateAug 21, 2017
Priority dateMar 20, 2015
Publication dateJul 23, 2019
Grant dateJul 23, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A system for cluster management comprises a status monitor and an instance replacement manager. The status monitor is for monitoring status of an instance of a set of instances on a cluster provider. The instance replacement manager is for determining a replacement strategy for the instance in the event the instance does not respond. The replacement strategy for the instance is based at least in part on a management criteria for on-demand instances and spot instances on the cluster provider.

First claim

Opening claim text (preview).

What is claimed is: 1. A system for cluster management, comprising: a processor; and a memory coupled with the processor, wherein the memory is configured to provide the processor with instructions which when executed cause the processor to: monitor status of an instance of a set of instances on a cluster provider; and determine a replacement strategy for the instance in response to a determination the instance does not respond, wherein the replacement strategy for the instance is based at least in part on a management criteria for on-demand instances and spot instances on the cluster provider, and wherein the determining of the replacement strategy comprises to: in response to a determination that the set of instances is to be stopped: determine whether to maintain a master on-demand instance; and in response to a determination to maintain the master on-demand instance, stop the set of instances except the master on-demand instance. 2. A system as in claim 1 , wherein the processor is further configured to: receive the management criteria. 3. A system as in claim 2 , wherein the management criteria comprises one or more of the following: a maximum number of on-demand instances or a minimum number of on-demand instances. 4. A system as in claim 2 , wherein the management criteria comprises one or more of the following: a maximum number of total instances or a minimum number of total instances. 5. A system as in claim 2 , wherein the management criteria comprises a budget limit. 6. A system as in claim 2 , wherein the management criteria comprises a failure criterion. 7. A system as in claim 2 , wherein the management criteria comprises a reserve criterion. 8. A system as in claim 2 , wherein the management criteria comprises a reserve poolsize. 9. A system as in claim 1 , wherein the processor is further configured to: determine a new set of instances to request based at least in part on the management criteria. 10. A system as in claim 9 , wherein the processor is further configured to: determine availability of the new set of instances on the cluster provider; and in response to a determination that there is availability, indicate to create the new set of instances. 11. A system as in claim 9 , wherein the determining of the replacement strategy comprises to: determine a request strategy based at least in part on a cluster availability and on the management criteria. 12. A system as in claim 1 , wherein the monitoring of the status of the instance includes to monitor the status of the instance periodically. 13. A system as in claim 1 , wherein the monitoring of the status of the instance includes to monitor a status of each instance of the set of instances. 14. A system as in claim 1 , wherein the monitoring of the status of the instance includes to monitor a status of each spot instance of the set of instances. 15. A system as in claim 1 , wherein the replacement strategy comprises replacing the instance with a spot instance from a reserve pool. 16. A system as in claim 1 , wherein the replacement strategy comprises replacing the instance with an on-demand instance in response to a determination that this is allowed under the management criteria. 17. A system as in claim 1 , wherein the replacement strategy comprises monitoring for a replacement instance. 18. A system as in claim 1 , wherein the replacement strategy comprises stopping the set of instances. 19. A system as in claim 18 , wherein the replacement strategy comprises saving the state of the set of instances. 20. A system as in claim 18 , wherein the replacement strategy comprises maintaining one on-demand instance of the set of instances. 21. A method for cluster management, comprising: monitoring status of an instance of a set of instances on a cluster provider; and determining, using a processor, a replacement strategy for the instance in response to a determination the instance does not respond, wherein the replacement strategy for the instance is based at least in part on a management criteria for on-demand instances and spot instances on the cluster provider, and wherein the determining of the replacement strategy comprises: in response to a determination that the set of instances is to be stopped: determining whether to maintain a master on-demand instance; and in response to a determination to maintain the master on-demand instance, stopping the set of instances except the master on-demand instance. 22. A computer program product for cluster management, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: monitoring status of an instance of a set of instances on a cluster provider; and determining, a replacement strategy for the instance in response to a determination the instance does not respond, wherein the replacement strategy for the instance is based at least in part on a management criteria for on-demand instances and spot instances on the cluster provider, and wherein the determining of the replacement strategy comprises: in response to a determination that the set of instances is to be stopped: determining whether to maintain a master on-demand instance; and in response to a determination to maintain the master on-demand instance, stopping the set of instances except the master on-demand instance.

Assignees

Inventors

Classifications

  • Service on demand, e.g. definition and deployment of services in real time · CPC title

  • Monitoring · CPC title

  • wherein the managed service relates to distributed or central networked applications · CPC title

  • by checking functioning · CPC title

  • where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10361928B2 cover?
A system for cluster management comprises a status monitor and an instance replacement manager. The status monitor is for monitoring status of an instance of a set of instances on a cluster provider. The instance replacement manager is for determining a replacement strategy for the instance in the event the instance does not respond. The replacement strategy for the instance is based at least i…
Who is the assignee on this patent?
Databricks Inc
What technology area does this patent fall under?
Primary CPC classification H04L41/5051. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Jul 23 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).