Resource Conservation for Containerized Systems

• US 20200133731A1
• Filed: 10/30/2018
• Published: 04/30/2020
• Est. Priority Date: 10/30/2018
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google LLC (Alphabet Inc.)
• Inventors: Barbara, Justin Santa, Hockin, Timothe, Bailey, Robert, Johnson, Jeffrey
• Granted Patent: US 10,922,138 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 9/50 Allocation of resources, e.g. of the central processing unit [CPU]
• CPC Class Codes: G06F 9/5005 to service a request
• CPC Class Codes: G06F 9/5011 the resources being hardware resources other than CPUs, Servers and Terminals
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/5022 Mechanisms to release resources
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A method for conserving resources in a distributed system includes receiving an event-criteria list from a resource controller. The event-criteria list includes one or more events watched by the resource controller and the resource controller controls at least one target resource and is configured to respond to events from the event-criteria list that occur. The method also includes determining whether the resource controller is idle. When the resource controller is idle, the method includes terminating the resource controller, determining whether any event from the event-criteria list occurs after terminating the resource controller, and, when at least one event from the event-criteria list occurs after terminating the resource controller, recreating the resource controller.

Claims

1. A method comprising:

receiving, at data processing hardware, an event-criteria list from a resource controller, the event-criteria list comprising one or more events watched by the resource controller, the resource controller controlling at least one target resource and configured to respond to events from the event-criteria list that occur;

determining, by the data processing hardware, whether the resource controller is idle; and

when the resource controller is idle;

terminating, by the data processing hardware, the resource controller;

determining, by the data processing hardware, whether any event from the event-criteria list occurs after terminating the resource controller; and

when at least one event from the event-criteria list occurs after terminating the resource controller, recreating, by the data processing hardware, the resource controller.

2. The method of claim 1, wherein determining whether the resource controller is idle comprises polling the resource controller.

3. The method of claim 1, wherein determining whether the resource controller is idle comprises:

analyzing events that have occurred during a threshold period of time; and

determining that the resource controller is idle when no events on the event-criteria list have occurred within the threshold period of time.

4. The method of claim 1, wherein terminating the resource controller comprises scaling a deployment size of the resource controller to zero.

5. The method of claim 1, wherein recreating the resource controller comprises scaling a deployment size of the resource controller to one.

6. The method of claim 1, wherein the event-criteria list comprises a timer event.

7. The method of claim 1, wherein determining whether any event on the event-criteria list occurred comprises polling data to determine when events on the event-criteria list occur.

8. The method of claim 1, further comprising, after terminating the resource controller:

determining, by the data processing hardware, whether a terminate time period since terminating the resource controller satisfies a threshold period of time; and

in response to determining that the terminate time period does satisfy the threshold period of time, recreating, by the data processing hardware, the resource controller.

9. The method of claim 1, further comprising, after terminating the resource controller:

determining, by the data processing hardware, whether the resource controller requires maintenance or reconfiguration; and

in response to determining that the resource controller requires maintenance or reconfiguration, recreating, by the data processing hardware, the resource controller.

10. The method of claim 1, wherein receiving the event-criteria list from the resource controller comprises receiving a plurality of event-criteria lists from a plurality of resource controllers executing simultaneously, each event-criteria list associated with a respective resource controller.

11. The method of claim 10, wherein a quantity of the resource controllers executing simultaneously is based upon a total amount of available system resources.

12. The method of claim 10, further comprising:

determining, by the data processing hardware, whether any event on multiple event-criteria lists occurred simultaneously; and

in response to determining that an event on multiple event-criteria lists occurred simultaneously, recreating, by the data processing hardware, a group of resource controllers sequentially, each resource controller of the group of resource controllers associated with a respective event-criteria list of the multiple event-criteria lists.

13. The method of claim 12, wherein recreating the group of resource controllers sequentially comprises recreating the group of resource controllers sequentially based on a priority of each resource controller.

14. The method of claim 1, further comprising recreating, by the data processing hardware, the resource controller based on a system metric.

15. The method of claim 14, wherein the system metric comprises a measure of system resources.

16. The method of claim 1, wherein the event-criteria list comprises a dynamic event-criteria list.

17. The method of claim 1, further comprising, prior to terminating the resource controller when the resource controller is idle:

determining, by the data processing hardware, whether a measure of system resources satisfies a system resource threshold; and

when both the measure of system resources satisfies the system resource threshold and the resource controller is idle, terminating, by the data processing hardware, the resource controller.

18. The method of claim 17, wherein the measure of system resources comprises a measure of system processing/computing, network access, storage, and/or memory resources.

19. The method of claim 1, wherein receiving the event-criteria list from the resource controller comprises receiving the event-criteria list from an HTTP endpoint.

20. The method of claim 1, wherein the resource controller is associated with a system resource reservation and terminating the resource controller removes the system resource reservation.

21. A system comprising:

data processing hardware; and

memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed on the data processing hardware cause the data processing hardware to perform operations comprising;

receiving an event-criteria list from a resource controller, the event-criteria list comprising one or more events watched by the resource controller, the resource controller controlling at least one target resource and configured to respond to events from the event-criteria list that occur;

determining whether the resource controller is idle; and

when the resource controller is idle;

terminating the resource controller;

determining whether any event from the event-criteria list occurs after terminating the resource controller; and

when at least one event from the event-criteria list occurs after terminating the resource controller, recreating the resource controller.

22. The system of claim 21, wherein determining whether the resource controller is idle comprises polling the resource controller.

23. The system of claim 21, wherein determining whether the resource controller is idle comprises:

analyzing events that have occurred during a threshold period of time; and

determining that the resource controller is idle when no events on the event-criteria list have occurred within the threshold period of time.

24. The system of claim 21, wherein terminating the resource controller comprises scaling a deployment size of the resource controller to zero.

25. The system of claim 21, wherein recreating the resource controller comprises scaling a deployment size of the resource controller to one.

26. The system of claim 21, wherein the event-criteria list comprises a timer event.

27. The system of claim 21, wherein determining whether any event on the event-criteria list occurred comprises polling data to determine when events on the event-criteria list occur.

28. The system of claim 21, wherein the operations further comprise, after terminating the resource controller:

determining whether a terminate time period since terminating the resource controller satisfies a threshold period of time; and

in response to determining that the terminate time period does satisfy the threshold period of time, recreating the resource controller.

29. The system of claim 21, wherein the operations further comprise, after terminating the resource controller:

determining whether the resource controller requires maintenance or reconfiguration; and

in response to determining that the resource controller requires maintenance or reconfiguration, recreating the resource controller.

30. The system of claim 21, wherein receiving the event-criteria list from the resource controller comprises receiving a plurality of event-criteria lists from a plurality of resource controllers executing simultaneously, each event-criteria list associated with a respective resource controller.

31. The system of claim 30, wherein a quantity of resource controllers executing simultaneously is based upon a total amount of available system resources.

32. The system of claim 30, wherein the operations further comprise:

determining whether any event on multiple event-criteria lists occurred simultaneously; and

in response to determining that an event on multiple event-criteria lists occurred simultaneously, recreating a group of resource controllers sequentially, each resource controller of the group of resource controllers associated with a respective event-criteria list of the multiple event-criteria lists.

33. The system of claim 32, wherein recreating the group of resource controllers sequentially comprises recreating the group of resource controllers sequentially based on a priority of each resource controller.

34. The system of claim 21, wherein the operations further comprise recreating the resource controller based on a system metric.

35. The system of claim 34, wherein the system metric comprises a measure of system resources.

36. The system of claim 21, wherein the event-criteria list comprises a dynamic event-criteria list.

37. The system of claim 21, wherein the operations further comprise, prior to terminating the resource controller when the resource controller is idle:

determining whether a measure of system resources satisfies a system resource threshold; and

when both the measure of system resources satisfies the system resource threshold and the resource controller is idle, terminating the resource controller.

38. The system of claim 37, wherein the measure of system resources comprises a measure of system processing/computing, network access, storage, and/or memory resources.

39. The system of claim 21, wherein receiving the event-criteria list from the resource controller comprises receiving the event-criteria list from an HTTP endpoint.

40. The system of claim 21, wherein the resource controller is associated with a system resource reservation and terminating the resource controller removes the system resource reservation.