Load balancing and fault tolerant service in a distributed data system
US-11080100-B2 · Aug 3, 2021 · US
US12353924B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12353924-B2 |
| Application number | US-202318334053-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 13, 2023 |
| Priority date | Feb 12, 2015 |
| Publication date | Jul 8, 2025 |
| Grant date | Jul 8, 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.
Techniques for load balancing and fault tolerant service are described. An apparatus may comprise load balancing and fault tolerant component operative to execute a load balancing and fault tolerant service in a distributed data system. The load balancing and fault tolerant service distributes a load of a task to a first node in a cluster of nodes using a routing table. The load balancing and fault tolerant service stores information to indicate the first node from the cluster of nodes is assigned to perform the task. The load balancing and fault tolerant service detects a failure condition for the first node. The load balancing and fault tolerant service moves the task to a second node from the cluster of nodes to perform the task for the first node upon occurrence of the failure condition.
Opening claim text (preview).
The invention claimed is: 1. A method, comprising: distributing, by a load balancing and fault tolerant service, a load of a task to a first node in a cluster of nodes using a routing table; replicating the routing table to the nodes of the cluster to notify the nodes of the cluster that the load of the task is assigned to the first node; monitoring, by a monitoring thread, health of the nodes of the cluster; and updating the routing table at each node of the cluster based upon a workload of the cluster being rebalanced based upon a health of the first node. 2. The method of claim 1 , wherein the updating comprises: in response to the monitoring thread detecting a failure of the first node as the health of the first node, rebalancing the workload of the cluster and updating the routing table at each node of the cluster. 3. The method of claim 1 , comprising: utilizing, by the load balancing and fault tolerant service, the routing table to distribute storage virtual machine backup tasks to the nodes of the cluster. 4. The method of claim 1 , comprising: utilizing the routing table for storing records and identifiers of nodes current owning tasks. 5. The method of claim 1 , comprising: populating the routing table with a last-owning-node list to indicate which nodes were last known owners of storage virtual machines within a replicated routing table. 6. The method of claim 1 , comprising: populating the routing table with a state and current operation of a disaster recovery relationship created between a first storage virtual machine having a current task and a second storage virtual machine receiving the current task. 7. The method of claim 1 , comprising: populating the routing table with a state and current operation of a disaster recovery relationship created between a first storage virtual machine and a second storage virtual machine, wherein the first storage virtual machine is performing a backup operation to create a backup that the second storage virtual machine receives. 8. The method of claim 1 , comprising: utilizing the routing table to track a current operation and statistics of previous operations. 9. The method of claim 1 , comprising: utilizing the routing table to track progress of a failover process. 10. The method of claim 1 , comprising: in response to a node failing and the routing table being updated based upon the node failing, invoking a process on a new node to becoming involved with a current task of the node that has failed. 11. A computing device, comprising: a memory comprising instructions; and a processor coupled with the memory, the processor configured to execute the instructions to cause the processor to perform operations comprising: distributing, by a load balancing and fault tolerant service, a load of a task to a first node in a cluster of nodes using a routing table; replicating the routing table to the nodes of the cluster to notify the nodes of the cluster that the load of the task is assigned to the first node; monitoring, by a monitoring thread, health of the nodes of the cluster; and updating the routing table at each node of the cluster based upon a workload of the cluster being rebalanced based upon a health of the first node. 12. The computing device of claim 11 , wherein the operations comprise: populating the routing table with a last-owning-node list to indicate which nodes were last known owners of storage virtual machines within a replicated routing table. 13. The computing device of claim 11 , wherein the operations comprise: populating the routing table with a state and current operation of a disaster recovery relationship created between a first storage virtual machine having a current task and a second storage virtual machine receiving the current task. 14. The computing device of claim 11 , wherein the operations comprise: populating the routing table with a state and current operation of a disaster recovery relationship created between a first storage virtual machine and a second storage virtual machine, wherein the first storage virtual machine is performing a backup operation to create a backup that the second storage virtual machine receives. 15. The computing device of claim 11 , wherein the operations comprise: utilizing the routing table to track a current operation and statistics of previous operations. 16. The computing device of claim 11 , wherein the operations comprise: in response to the monitoring thread detecting a reactivation of the first node after a failure, rebalancing the workload of the cluster and updating the routing table at each node of the cluster. 17. The computing device of claim 11 , wherein the operations comprise: in response to the monitoring thread detecting that the first node has been added to the cluster, rebalancing the workload of the cluster and updating the routing table at each node of the cluster. 18. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor, cause the processor to perform operations comprising: distributing, by a load balancing and fault tolerant service, a load of a task to a first node in a cluster of nodes using a routing table; replicating the routing table to the nodes of the cluster to notify the nodes of the cluster that the load of the task is assigned to the first node; monitoring, by a monitoring thread, health of the nodes of the cluster; and updating the routing table at each node of the cluster based upon a workload of the cluster being rebalanced based upon a health of the first node. 19. The non-transitory computer-readable storage medium of claim 18 , wherein the operations comprise: in response to the monitoring thread detecting a failure of the first node as the health of the first node, rebalancing the workload of the cluster and updating the routing table at each node of the cluster. 20. The non-transitory computer-readable storage medium of claim 18 , wherein the operations comprise: utilizing, by the load balancing and fault tolerant service, the routing table to distribute storage virtual machine backup tasks to the nodes of the cluster.
for load management (allocation of a server based on load conditions G06F9/505; load rebalancing G06F9/5083; redistributing the load in a network by a load balancer H04L67/1029) · CPC title
without idle spare hardware · CPC title
involving virtual machines · CPC title
by reconfiguration of node membership · CPC title
Real-time · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.