Database systems and related queue management methods
US-2017061364-A1 · Mar 2, 2017 · US
US10193977B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10193977-B2 |
| Application number | US-201615142040-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 29, 2016 |
| Priority date | Apr 29, 2016 |
| Publication date | Jan 29, 2019 |
| Grant date | Jan 29, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and systems of managing workloads and resources for tenants structured as a hierarchical tenant queue defining a resource distribution policy. The tenants are modified and the system responds with dynamic adjustments to the hierarchical tenant queue and workload distribution. A rule-based workload management engine defines rules for actions for the workload to respond to the dynamic update.
Opening claim text (preview).
What is claimed is: 1. A process for managing workloads by a distributed resource management system of a distributed computing system, the process comprising: receiving a tenant update for a hierarchical queue, the hierarchical queue comprising tenants and sub-tenants, the tenant update identifying a modification to a tenant or sub-tenant of the hierarchical queue; retrieving, by a rule-based workload management engine, a rule having a tenant event corresponding to the tenant update, wherein the rule-based workload management engine retrieves the rule from a database storing rules, each rule stored in the database including a tenant event identifying a tenant or sub-tenant of the tenants or sub-tenants the rule is applicable to and an action for one or more workloads of the tenant or sub-tenant; determining, from the retrieved rule, the action for the one or more workloads of the tenant or sub-tenant identified in the tenant event of the retrieved rule, each of the one or more workloads of the tenant or sub-tenant identified associated with a resource request; and applying the action for the one or more workloads of the tenant or sub-tenant, without interrupting execution of any workloads of other tenants or sub-tenants of the hierarchical queue. 2. The process of claim 1 , the action for the one or more workloads of the tenant or sub-tenant comprises killing at least one of the one or more workloads, moving at least one of the one or more workloads, and suspending at least one of the one or more workloads. 3. The process of claim 1 , wherein each rule further includes a workload matching expression. 4. The process of claim 3 , wherein retrieving further comprises identifying, by the rule-based workload management engine, the rule corresponding to the tenant event, and determining which ones of the one or more workloads of the tenant or sub-tenant identified in the tenant event of the retrieved rule match the workload matching expression, and wherein applying the action comprises applying the action to the determined ones of the one or more workflows of the tenant or sub-tenant. 5. The process of claim 3 , further comprising, by the rule-based workload management engine: retrieving a set of rules having a tenant event corresponding to the tenant update; filtering the set of rules using the workload matching expressions; upon determining that the filtered set of rules include multiple rules, ordering the filtered set of rules based on a priority sequence; and returning actions for the one or more workloads for the tenant or sub-tenant from the ordered, filtered set of rules. 6. The process of claim 1 , wherein retrieving further comprises sending a request to the rule-based workload management engine, the request comprising the tenant update. 7. The process of claim 6 , further comprising determining that no rules correspond to the tenant update and returning one or more default rules to move the one or more workloads for the tenant or sub-tenant to a Lost&Found queue. 8. The process of claim 1 , wherein applying the action for the one or more workloads for the tenant or sub-tenant comprises applying a default action to move the one or more workloads to a Lost&Found queue. 9. The process of claim 8 , further comprising moving the one or more workloads from the Lost&Found queue back to the hierarchical queue. 10. The process of claim 1 , wherein the tenant update identifying a modification to a tenant or sub-tenant of the hierarchical queue comprises one of: deleting the tenant or sub-tenant from the hierarchical queue, adding the tenant or sub-tenant to the hierarchical queue, and moving a location of the tenant or sub-tenant in the hierarchical queue. 11. A device comprising a processor and a memory storing instructions to configure the processor with a rule-based workload management engine to: receive a tenant update for a hierarchical queue, the hierarchical queue comprising tenants and sub-tenants, the tenant update identifying a modification to a tenant or sub-tenant of the hierarchical queue; retrieve a rule having a tenant event corresponding to the tenant update, wherein the rule is retrieved from a database storing rules, each rule stored in the database including a tenant event identifying a tenant or sub-tenant of the tenants or sub-tenants the rule is applicable to and an action for one or more workloads of the tenant or sub-tenant; determine, from the retrieved rule, the action for the one or more workloads of the tenant or sub-tenant identified in the tenant event of the retrieved rule, each of the one or more workloads of the tenant or sub-tenant identified associated with a resource request; and apply the action for the one or more workloads of the tenant or sub-tenant without interrupting execution of any workloads of other tenants or sub-tenants of the hierarchical queue. 12. The device of claim 11 , wherein the action for the one or more workloads of the tenant or sub-tenant comprises killing at least one of the one or more workloads, moving at least one of the one or more workloads, and suspending at least one of the one or more workloads. 13. The device of claim 11 , wherein each rule further includes a workload matching expression. 14. The device of claim 11 , wherein the rule-based workload management engine has rules with a component for a workload matching expression to determine that the rule is applicable to the workload memory stores instructions to further configure the processor with the rule-based workload management engine to retrieve a rule by identifying the rule corresponding to the tenant event, determining which ones of the one or more workloads of the tenant or sub-tenant identified in the tenant event of the retrieved rule match the workload matching expression, and to apply the action to the determined ones of the one or more workflows of the tenant or sub-tenant. 15. The device of claim 14 , wherein the memory stores instructions to further configure the processor with the rule-based workload management engine to: retrieve a set of rules having a tenant event corresponding to the tenant update; filter the set of rules using the workload matching expressions; upon determining that the filtered set of rules include multiple rules, ordering the filtered set of rules based on a priority sequence; and returning actions for the one or more workloads for the tenant or sub-tenant from the ordered, filtered set of rules. 16. The device of claim 14 , wherein the memory stores instructions to further configure the processor with the rule-based workload management engine to determined that no rules correspond to the tenant update and returning one or more default rules to move the one or more workloads for the tenant or sub-tenant to a Lost&Found queue. 17. The device of claim 14 , wherein the memory stores instructions to further configure the processor with the rule-based workload management engine to move the one or more workloads from the Lost&Found queue back to the hierarchical queue. 18. The device of claim 11 , wherein the action for the one or more workloads for the tenant or sub-tenant is applied by applying a default action to move the one or more workloads to a Lost&Found queue. 19. The device of claim 11 , wherein the tenant update identifying a modification to a tenant or sub-tenant of the hierarchical queue comprises one of: deleting the tenant or sub-tenant from the hierarchical queue, adding the tenant or sub-tenant to the hierarchical queue, and moving a location of the tenant or sub-
Electricity · mapped topic
Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title
Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components · CPC title
Prioritising resource allocation or reservation requests · CPC title
for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.