Zone balancing in a multi cluster database system
US-11372820-B1 · Jun 28, 2022 · US
US2023103223A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2023103223-A1 |
| Application number | US-202117484754-A |
| Country | US |
| Kind code | A1 |
| Filing date | Sep 24, 2021 |
| Priority date | Sep 24, 2021 |
| Publication date | Mar 30, 2023 |
| Grant date | — |
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.
Various examples described herein are directed to systems and methods for managing a cloud-implemented database management application, the method comprising. At least one cloud service may receive a request from a first user group to launch a first instance of the database management application. The at least one cloud service may access a version metadata record for the database management application and use the version metadata record to launch the first instance of the database management application. The at least one cloud service may store first instance metadata for first instance of the database management application at a container management metadata persistence associated with the first instance of the database management application. The first instance metadata may comprise an indication of the first container image.
Opening claim text (preview).
What is claimed is: 1 . A system for managing a cloud-implemented database management application, the system comprising: at least one processor programmed to perform operations comprising: receiving, by at least one cloud service executing in a cloud environment, a request from a first user group to launch a first instance of the database management application; accessing, by the at least one cloud service, a version metadata record for the database management application, the version metadata record indicating a first container image associated with a first version of the database management application; launching, by the at least one cloud service, the first instance of the database management application at the cloud environment using the first container image; and storing, by the at least one cloud service, first instance metadata for first instance of the database management application at a container management metadata persistence associated with the first instance of the database management application, the first instance metadata comprising an indication of the first container image. 2 . The system of claim 1 , the operations further comprising: receiving, by the at least one cloud service, new version metadata for a new version of the database management application, the new version metadata indicating a new container image different than the first container image; adding, by the at least one cloud service, the new version metadata to the version metadata record for the database management application; and deleting, by the at least one cloud service, an indication of the first container image from the version metadata record. 3 . The system of claim 1 , the operations further comprising: determining, by a container management system executing at the cloud environment, that the first instance of the database management application has crashed; accessing, by the container management system, the first instance metadata; and using the first instance metadata, restarting the first version of the database management application. 4 . The system of claim 1 , the operations further comprising: determining, by a container management system executing at the cloud environment, that the first container has crashed; accessing, by the container management system, the first instance metadata from the container management metadata persistence; and relaunching the first container using the first container image indicated by the first instance metadata. 5 . The system of claim 1 , the operations further comprising: determining, by the at least one cloud service, that the version metadata record for the database management application is updated to refer to a second version of the database management application; upgrading, by the at least one cloud service, the first instance database management application to the second version of the database management application; adding to the first instance metadata, by the at least one cloud service, an indication of a second container image associated with a second version of the database management application; and deleting, by the at least one cloud service, the indication of the first container image from the first instance metadata. 6 . The system of claim 5 , the operations further comprising: before launching the first instance of the database management application, determining that a first maturity level field of the version metadata record indicates the first version; and after launching the first instance of the database management application, determining that the first maturity level field of the version metadata record indicates the second version. 7 . The system of claim 5 , the operations further comprising: accessing, by the at least one cloud service, an upgrade strategy map record associated with the database management application; before upgrading the first instance database management application to the second version of the database management application, determining, by the at least one cloud service, that the upgrade strategy map record indicates that it is permissible to upgrade the first version of the database management application to the second version of the database management application. 8 . The system of claim 1 , the operations further comprising: accessing, by the first cloud service executing at the cloud environment, an upgrade strategy record associated with the first version of the database management application; and writing the set of target versions indicated for the first version of the database management application at the upgrade strategy record to the upgrade metadata associated with the first user group instance of the first version of the database management application. 9 . A method for managing a cloud-implemented database management application, the method comprising: receiving, by at least one cloud service executing in a cloud environment, a request from a first user group to launch a first instance of the database management application; accessing, by the at least one cloud service, a version metadata record for the database management application, the version metadata record indicating a first container image associated with a first version of the database management application; launching, by the at least one cloud service, the first instance of the database management application at the cloud environment using the first container image; and storing, by the at least one cloud service, first instance metadata for first instance of the database management application at a container management metadata persistence associated with the first instance of the database management application, the first instance metadata comprising an indication of the first container image. 10 . The method of claim 9 , further comprising: receiving, by the at least one cloud service, new version metadata for a new version of the database management application, the new version metadata indicating a new container image different than the first container image; adding, by the at least one cloud service, the new version metadata to the version metadata record for the database management application; and deleting, by the at least one cloud service, an indication of the first container image from the version metadata record. 11 . The method of claim 9 , further comprising: determining, by a container management system executing at the cloud environment, that the first instance of the database management application has crashed; accessing, by the container management system, the first instance metadata; and using the first instance metadata, restarting the first version of the database management application. 12 . The method of claim 9 , further comprising: determining, by a container management system executing at the cloud environment, that the first container has crashed; accessing, by the container management system, the first instance metadata from the container management metadata persistence; and relaunching the first container using the first container image indicated by the first instance metadata. 13 . The method of claim 9 , further comprising: determining, by the at least one cloud service, that the version metadata record for the database management application is updated to refer to a second version of the database management application; upgrading, by the at least one cloud service, the first instance database management application to the second version of the database management application; adding to the first instance metadata, by the at least one cloud service, an indication of a second conta
Database migration support · CPC title
Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477) · CPC title
Starting, stopping, suspending or resuming virtual machine instances · CPC title
Hypervisor-specific management and integration aspects · CPC title
Creating, deleting, cloning virtual machine instances · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.