You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The goal of this task is to create a list of components that are doing something at runtime without user interaction on ws-master or have some state inside. For instance, DockerAbandonedResourcesCleaner is making some periodical cleaning or MachineTokenRegistry. We need this list because in case if we will run several masters in parallel (#8547) we need to make sure that they can work together and not brake anything.
The text was updated successfully, but these errors were encountered:
So the brief overview of existing self-executed components on the master side shows us a following:
Without an state inside:
WsMasterAnalyticsAddresser periodically sends activity ping to the usage(?) analytinc script;
DockerAbandonedResourcesCleaner which is periodically cleans up abandoned docker containers and networks
With state:
WorkspaceActivityManager holds the WS activity timestamps inside. Can potettially stops active workspaces when activity pings will go to another instance.
MachineTokenRegistry and related stuff - holds the machine tokens for every WS and can cause undefined states.
Description
The goal of this task is to create a list of components that are doing something at runtime without user interaction on ws-master or have some state inside. For instance, DockerAbandonedResourcesCleaner is making some periodical cleaning or MachineTokenRegistry. We need this list because in case if we will run several masters in parallel (#8547) we need to make sure that they can work together and not brake anything.
The text was updated successfully, but these errors were encountered: