Dynamic Adjustment Of Application Resources In A Distributed Computing System

• US 20190220315A1
• Filed: 01/12/2018
• Published: 07/18/2019
• Est. Priority Date: 01/12/2018
• Status: Active Grant

• Current Assignee: Robin Systems, Inc. (Rakuten Group, Inc.)
• Original Assignee: Robin Systems, Inc. (Rakuten Group, Inc.)
• Inventors: Vallala, Shravan Kumar, Alluboyina, Ravi Kumar
• Granted Patent: US 10,846,137 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3442 for planning or managing the needed capacity
• CPC Class Codes: G06F 12/0253 Garbage collection, i.e. reclamation of unreferenced memory
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 9/455 Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/48 Program initiating; Program switching, e.g. by interrupt
• CPC Class Codes: G06F 9/5016 the resource being the memory
• CPC Class Codes: G06F 9/5033 considering data affinity
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455

Abstract

A new snapshot of a storage volume is created by instructing computing nodes to suppress write requests. Once pending write requests from the computing nodes are completed, storage nodes create a new snapshot for the storage volume by allocating a new segment to the new snapshot and finalizes and performs garbage collection with respect to segments allocated to the previous snapshot. Subsequent write requests to the storage volume are then performed on the segments allocated to the new snapshot. An orchestration layer implements a bundled application that is provisioned with virtualized storage and computation resources. A snapshot of the application may be created and used to rollback or clone the application. The amount of processing cores, memory, and containers of the bundled application may be increased or decreased based on usage. Components of the bundled application may be assigned to nodes to satisfy affinity and anti-affinity rules.

Claims

1. A method comprising:

monitoring, by a first computing device, loading of a subject application instance of a bundled application executing in a first container on the first computing device, the bundled application including a plurality of application instances executing on a plurality of computing devices, the subject application executing on a subject computing device that is one of the first computing device and a second computing device of the plurality of computing devices;

(a) determining, by the first computing device, that loading of the subject application instance exceeds a first threshold condition; and

in response to (a), increasing, by the first computing device, an allocation of processing cores to the first container.

2. The method of claim 1, further comprising:

in response to (a), increasing an allocation of memory to the first container.

3. The method of claim 1, further comprising:

(b) determining, by the first computing device, that loading of the subject application instance is below a second threshold condition; and

in response to (b), decreasing the allocation of processing cores to the first container.

4. The method of claim 1, further comprising:

mounting, by the first computing device, a virtual file system to the first container; and

storing, by the subject computing device, a virtual system resource file in the virtual file system;

wherein increasing the allocation of processing cores to the first container comprises changing a number of processors stored in the virtual system resource file.

5. The method of claim 1, further comprising:

receiving, by a kernel executing on the subject computing device, a system call to retrieve a number of processors of the subject computing device;

intercepting, by the kernel, the system call; and

returning, by the kernel, in response to the system call, the allocation of processing cores to the first container.

6. The method of claim 1, wherein increasing, by the first computing device, the allocation of processing cores to the first container comprises:

(b) determining, by the first computing device, that the subject computing device does not have available processing cores to permit increasing of the allocation; and

in response to (b), transferring the first container from the subject computing device to a third computing device.

7. The method of claim 6, wherein transferring the first container from the subject computing device to the third computing device comprises:

stopping the first container;

creating a new container on the third computing device; and

transferring a state of the first container to the new container.

8. The method of claim 7, wherein transferring the first container from the subject computing device to the third computing device comprises:

executing a pre-transfer hook with respect to the subject application instance prior to stopping the first container, the pre-transfer hook being a first script; and

executing a post-transfer hook with respect to the subject application instance after transferring the state of the first container to the new container, the post-transfer hook being a second script.

9. The method of claim 1, further comprising:

(b) determining, by the first computing device, that loading of the subject application instance exceeds a second threshold condition; and

in response to (b);

creating a new container on the third computing device; and

loading a copy of the subject application instance into the new container.

10. The method of claim 1, further comprising:

(b) determining, by the first computing device, that loading of the subject application instance is below a second threshold condition; and

in response to (b), shutting down the first container.

11. A system comprising:

a first computing device programmed to;

monitor loading of a subject application instance of a bundled application executing in a first container on the first computing device, the bundled application including a plurality of application instances executing on a plurality of computing devices, the subject application executing one a subject computing device that is one of the first computing device and a second computing device of the plurality of computing devices;

when (a) loading of the subject application instance exceeds a first threshold condition, increase, by the first computing device, an allocation of processing cores to the first container.

12. The system of claim 11, wherein the first computing device is further programmed to:

in response to (a), increase an allocation of memory to the first container.

13. The system of claim 11, wherein the first computing device is further programmed to:

when loading of the subject application instance is below a second threshold condition, decrease the allocation of processing cores to the first container.

14. The system of claim 11, wherein the first computing device is further programmed to:

mount a virtual file system to the first container; and

store a virtual system resource file in the virtual file system;

increase the allocation of processing cores to the first container by changing a number of processors stored in the virtual system resource file.

15. The system of claim 11, further comprising the subject computing device, the subject computing device being further programmed to:

receive, by a kernel executing on the subject computing device, a system call to retrieve a number of processors of the subject computing device;

intercept, by the kernel, the system call; and

return, by the kernel, in response to the system call, the allocation of processing cores to the first container.

16. The system of claim 11, wherein the first computing device is further programmed to increase the allocation of processing cores to the first container by:

(b) determining, by the first computing device, that the subject computing device does not have available processing cores to permit increasing of the allocation; and

in response to (b), transferring the first container from the subject computing device to a third computing device.

17. The system of claim 16, wherein the first computing device is further programmed to transfer the first container from the subject computing device to the third computing device by:

stopping the first container;

creating a new container on the third computing device; and

transferring a state of the first container to the new container.

18. The system of claim 17, wherein the first computing device is further programmed to transfer the first container from the subject computing device to the third computing device by:

executing a pre-transfer hook with respect to the subject application instance prior to stopping the first container, the pre-transfer hook being a first script; and

executing a post-transfer hook with respect to the subject application instance after transferring the state of the first container to the new container, the post-transfer hook being a second script.

19. The system of claim 11, wherein the first computing device is further programmed to:

(b) determine that loading of the subject application instance exceeds a second threshold condition; and

in response to (b);

create a new container on the third computing device; and

load a copy of the subject application instance into the new container.

20. The system of claim 11, wherein the first computing device is further programmed to:

(b) determine that loading of the subject application instance is below a second threshold condition; and

in response to (b), shut down the first container.