Automated load distribution for a group-based communication platform
US-2019334983-A1 · Oct 31, 2019 · US
US12450082B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12450082-B2 |
| Application number | US-202217705551-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 28, 2022 |
| Priority date | Mar 28, 2022 |
| Publication date | Oct 21, 2025 |
| Grant date | Oct 21, 2025 |
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.
A system detects a failed server in a cluster of servers, which are controlled by a master node to execute applications and store data, in service tiers, which correspond to sets of server performance characteristics, in storage domains, which correspond to server racks, in the cluster of servers. By accessing a cluster database, the system identifies applications installed on the failed server and any affinities that the identified applications have for any type of server, any service tier, and/or any storage domain. The system uses the cluster's current configuration to update the identified affinities for the identified applications. After the updated affinities for the identified applications is provided to the cluster database, a master node is enabled to identify replacement server(s), for the identified applications, and install the identified applications in the identified replacement server(s), thereby enabling the replacement server(s) to substitute for the failed server and store data.
Opening claim text (preview).
What is claimed is: 1. A system for a framework for managing the infrastructure for storage domains and service tiers, comprising: one or more processors; and a non-transitory computer readable medium storing a plurality of instructions, which when executed, cause the one or more processors to: detect a failed server in a cluster of servers, which are controlled by a master node to execute applications and store data, in service tiers, which correspond to sets of server performance characteristics, in storage domains, which correspond to server racks, in the cluster of servers; identify, by accessing a cluster database application installed in a server in the cluster of servers via a secure HTTPS port in the server, applications installed on the failed server and any affinities, based on high availability strategies, that the identified applications have for at least one of any type of server, any of the service tiers, and any of the storage domains, update, by accessing the cluster database application via the secure HTTPS port, based on a current configuration of the cluster, the identified affinities for the identified applications, and enable, by providing the updated affinities for the identified applications in the cluster database application, the master node to identify at least one replacement server, for the identified applications, and install the identified applications in the at least one replacement server, thereby enabling the at least one replacement server to substitute for the failed server, store data, and improve on, high availability for the cluster. 2. The system of claim 1 , wherein the plurality of instructions further causes the processor to: allocate the servers for each of the service tiers in each of the storage domains in the cluster, in response to receiving specifications for creating storage domains which include service tiers; create the cluster database application by installing a database application in at least three servers in the storage domains; create the master nodes by installing a container control services application in at least two servers in the storage domains; prepare the service tiers for operation by installing a tier services application in at least one server in each of the service tiers; prepare the storage domains for operation by installing a domain services application in at least one server in each of the storage domains; and combine each allocated server into the cluster of servers. 3. The system of claim 1 , wherein the identified applications comprise at least one of the container control services application, the tier services application, the domain services application, and a database application. 4. The system of claim 1 , wherein the replacement server comprises one of an existing server in a same service tier and a same storage domain as the failed server and a replacement server which is added to the same service tier and the same storage domain as the failed server after the failed server has failed. 5. The system of claim 1 , wherein identifying any affinities comprises identifying a count for the identified applications based on at least one of a count of the storage domains, a count of the service tiers, and a high availability strategy. 6. The system of claim 5 , wherein providing the identified affinities comprises providing the identified count to the cluster database application which enables the master node to identify replacement servers for the identified applications, and install the identified count of the identified applications in the replacement servers, thereby enabling the replacement servers to substitute for the failed server and store data. 7. The system of claim 1 , wherein identifying any affinities further comprises identifying any taints that the identified applications have which repels at least one of any type of server, any of the service tiers, and any of the storage domains. 8. A computer-implemented method for framework for managing the infrastructure for storage domains and service tiers the computer-implemented method comprising: detecting a failed server in a cluster of servers, which are controlled by a master node to execute applications and store data, in service tiers, which correspond to sets of server performance characteristics, in storage domains, which correspond to server racks, in the cluster of servers; identifying, by accessing a cluster database application installed in a server in the cluster of servers via a secure HTTPS port in the server, applications installed on the failed server and any affinities, based on high availability strategies, that the identified applications have for at least one of any type of server, any of the service tiers, and any of the storage domains, updating, by accessing the cluster database application via the secure HTTPS port, based on a current configuration of the cluster, the identified affinities for the identified applications; and enabling, by providing the updated affinities for the identified applications in the cluster database application, the master node to identify at least one replacement server, for the identified applications, and install the identified applications in the at least one replacement server, thereby enabling the at least one replacement server to substitute for the failed server, store data, and improve on high availability for the cluster. 9. The computer-implemented method of claim 8 , wherein the computer-implemented method further comprises: allocating the servers for each of the service tiers in each of the storage domains in the cluster, in response to receiving specifications for creating storage domains which include service tiers; creating the cluster database application by installing a database application in at least three servers in the storage domains; creating the master nodes by installing a container control services application in at least two servers in the storage domains; preparing the service tiers for operation by installing a tier services application in at least one server in each of the service tiers; preparing the storage domains for operation by installing a domain services application in at least one server in each of the storage domains; and combining each allocated server into the cluster of servers. 10. The computer-implemented method of claim 8 , wherein the identified applications comprise at least one of the container control services application, the tier services application, the domain services application, and a database application. 11. The computer-implemented method of claim 8 , wherein the replacement server comprises one of an existing server in a same service tier and a same storage domain as the failed server and a replacement server which is added to the same service tier and the same storage domain as the failed server after the failed server has failed. 12. The computer-implemented method of claim 8 , wherein identifying any affinities comprises identifying a count for the identified applications based on at least one of a count of the storage domains, a count of the service tiers, and a high availability strategy. 13. The computer-implemented method of claim 12 , wherein providing the identified affinities comprises providing the identified count to the cluster database application which enables the master node to identify replacement servers for the identified applications, and install the identified count of the identified applications in the replacement servers, thereby enabling the replacement servers to substitute for the failed server and store data. 14. The computer-implemented method of cla
Configuring for program initiating, e.g. using registry, configuration files · CPC title
I/O management, e.g. providing access to device drivers or storage · CPC title
Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title
Distribution of virtual machine instances; Migration and load balancing · CPC title
in a storage system, e.g. in a DASD or network based storage system (drivers for digital recording or reproducing units G06F3/06; circuits for error detection or correction within digital recording or reproducing units G11B20/18; 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], H04L67/1097) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.