US 11,700,300 B2
Cluster resource management in distributed computing systems
Maneesh Sah, Sammamish, WA (US); Rushi Surla, Kenmore, WA (US); Arild Skjolsvold, Kenmore, WA (US); Xinhua Ji, Redmond, WA (US); and Jegan Devaraju, Redmond, WA (US)
Assigned to Microsoft Technology Licensing, LLC, Redmond, WA (US)
Filed by MICROSOFT TECHNOLOGY LICENSING, LLC, Redmond, WA (US)
Filed on Mar. 24, 2022, as Appl. No. 17/703,516.
Application 17/703,516 is a continuation of application No. 16/793,651, filed on Feb. 18, 2020, granted, now 11,297,130.
Application 16/793,651 is a continuation of application No. 15/582,038, filed on Apr. 28, 2017, granted, now 10,609,130, issued on Mar. 31, 2020.
Prior Publication US 2022/0272242 A1, Aug. 25, 2022
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 29/08 (2006.01); H04L 67/1008 (2022.01); H04L 67/1031 (2022.01); H04L 43/16 (2022.01); H04L 41/0816 (2022.01); H04L 41/0893 (2022.01); H04L 47/762 (2022.01); G06F 9/50 (2006.01); G06T 7/11 (2017.01); H04N 13/254 (2018.01); H04N 13/271 (2018.01); H04N 23/56 (2023.01); H04N 23/74 (2023.01); G06F 9/48 (2006.01); G06F 9/4401 (2018.01)
CPC H04L 67/1008 (2013.01) [G06F 9/505 (2013.01); G06F 9/5061 (2013.01); G06F 9/5083 (2013.01); G06T 7/11 (2017.01); H04L 41/0816 (2013.01); H04L 41/0893 (2013.01); H04L 43/16 (2013.01); H04L 47/762 (2013.01); H04L 67/1031 (2013.01); H04N 13/254 (2018.05); H04N 13/271 (2018.05); H04N 23/56 (2023.01); H04N 23/74 (2023.01); G06F 9/4401 (2013.01); G06F 9/4856 (2013.01); G06F 2209/505 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method implemented by a duster resource manager of managing resources among dusters in a distributed computing system, the dusters including first and second clusters individually containing multiple servers interconnected to one another by a computer network and managed by a first cluster controller and a second cluster controller, respectively, the method comprising:
the cluster resource manager receiving, via the computer network, status data from the first cluster controller of the first cluster, the status data representing a compute load experienced by the first cluster; and
generating and sending a resource removal message to the first cluster controller when the compute load of the first cluster in the status data is below a threshold, the resource removal message indicating that a server from the first cluster is reassigned to the second cluster, the resource removal message instructing the first cluster controller to create or update a configuration file indicating that the server is reassigned from the first cluster, and thereby causing the first cluster controller to subsequently ignore the reassigned server.