Automated management of content servers based on change in demand

A method comprising:

• using a computer to detect a change in demand for server resources across a first load-bearing system having content servers hosting content;
• in response to the change in demand, determining, from the content servers hosting the content, two or more content servers having a lowest priority level from a set of priority levels;
• in response to determining that two or more content servers have the lowest priority level, determining, from the two or more content servers, a first content server having a least number of active sessions and selecting, from the two or more content servers, the first content server;
• stopping client requests from being directed to the first content server based on determining the first content server having the least number of active sessions;
• based on determining the first content server having the least number of active sessions, determining to wait until existing active sessions have been terminated on the first content server before removing the first content server from the first load-bearing system;
• storing an entry in a table, wherein the entry is associated with the hosted content, and wherein the entry indicates a priority level, a minimum threshold of content servers, and a maximum threshold of content servers;
• removing the first content server from the first load-bearing system, in response to a total number of content servers on the first load-bearing system being greater than the minimum threshold of content servers associated with the hosted content;
• adding the removed first content server to a second load-bearing system having one or more other content servers hosting separate content, in response to a number of the one or more other content servers on the second load-bearing system being less than the maximum threshold of content servers associated with the separate hosted content, the second load-bearing system connected to the first load-bearing system via a network connection;
• causing the separate hosted content to be stored on the removed first content server;
• causing client requests for the separate hosted content to be directed to at least the removed first content server on the second load-bearing system;
• receiving a first content file on a second content server, wherein the second content server is at an idle state, wherein the idle state corresponds to a lowest priority level, and wherein the first content file is at a highest priority level;
• and
• setting a priority of the second content sever to the highest priority level based on the first content file.