Module expiration management
Systems, methods, and non-transitory computer readable media are provided for managing expiration of modules. An expiry dataset may be maintained. The expiry dataset may include a set of identifiers corresponding to a set of modules, a set of expiry values for the set of modules, and a set of termination tasks for the set of modules. A request to refresh a module may be received from a client. Responsive to the reception of the request, an expiry value and a termination task for the module within the expiry dataset may be updated. The expiry value may be independent of a timestamp associated with the request.
1. A system comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the system to perform:
maintaining an expiry dataset, the expiry dataset including a set of identifiers corresponding to a set of modules, a set of expiry values for the set of modules, and a set of termination tasks for the set of modules;
receiving, by a first module manager of the system, a request to refresh a module from a client, wherein the first module manager manages module refresh requests along with one or more other module managers from multiple clients including the client; and
responsive to the reception of the request, updating a first expiry value and a first termination task for the module within the expiry dataset, wherein the first expiry value is independent of a timestamp associated with the request.
2. The system of claim 1 , wherein updating the first expiry value includes replacing the first expiry value with a second expiry value comprising a random number.
3. The system of claim 2 , wherein the random number includes a thirty-two bit number.
4. The system of claim 2 , wherein the the first expiry value is replaced with the second expiry value without reading the first expiry value.
5. The system of claim 1 , wherein updating the first expiry value includes replacing the first expiry value with a second expiry value comprising an incremented version number.
6. The system of claim 1 , wherein the first termination task terminating the module at a future time.
7. The system of claim 6 , wherein updating the first termination task includes canceling the first termination task and creating a new second termination task.
8. A method implemented by a computing system including one or more processors and storage media storing machine-readable instructions, wherein the method is performed using the one or more processors, the method comprising:
maintaining an expiry dataset, the expiry dataset including a set of identifiers corresponding to a set of modules, a set of expiry values for the set of modules, and a set of termination tasks for the set of modules;
receiving, by a first module manager of the system, a request to refresh a module from a client, wherein the first module manager manages module refresh requests along with one or more other module managers from multiple clients including the client; and
responsive to the reception of the request, updating a first expiry value and a first termination task for the module within the expiry dataset, wherein the first expiry value is independent of a timestamp associated with the request.
9. The method of claim 8 , wherein updating the first expiry value includes replacing the first expiry value with a second expiry value comprising a random number.
10. The method of claim 9 , wherein the random number includes a thirty-two bit number.
11. The method of claim 9 , wherein the the first expiry value is replaced with the second expiry value without reading the first expiry value.
12. The method of claim 8 , wherein updating the first expiry value includes replacing the first expiry value with a second expiry value comprising an incremented version number.
13. The method of claim 8 , wherein the first termination task includes terminating the module at a future time.
14. The method of claim 13 , wherein updating the first termination task includes canceling the first termination task and creating a new second termination task.
15. A non-transitory computer readable medium comprising instructions that, when executed, cause one or more processors to perform:
maintaining an expiry dataset, the expiry dataset including a set of identifiers corresponding to a set of modules, a set of expiry values for the set of modules, and a set of termination tasks for the set of modules;
receiving, by a first module manager of the system, a request to refresh a module from a client, wherein the first module manager manages module refresh requests along with one or more other module managers from multiple clients including the client; and
responsive to the reception of the request, updating a first expiry value and a first termination task for the module within the expiry dataset, wherein the first expiry value is independent of a timestamp associated with the request.
16. The non-transitory computer readable medium of claim 15 , wherein updating the first expiry value includes replacing the first expiry value with a second expiry value comprising a random number.
17. The non-transitory computer readable medium of claim 16 , wherein the random number includes a thirty-two bit number.
18. The non-transitory computer readable medium of claim 16 , wherein the the first expiry value is replaced with the second expiry value without reading the first expiry value.
19. The non-transitory computer readable medium of claim 15 , wherein updating the first expiry value includes replacing the first expiry value with a second expiry value comprising an incremented version number.
20. The non-transitory computer readable medium of claim 15 , wherein the first termination task includes terminating the module at a future time.