Sticky session data migration

Abstract

Techniques for migrating virtual desktop sessions in a sticky session environment are disclosed. A load balancer can select a first server to service requests sent by a client, and select a second server to store session data associated with the requests. The load balancer can cause the first server to initiate a transmission of the session data to the second server. The load balancer can forward the requests to the second server in response to determining that a load-related event has occurred. A method, system, and computer-readable medium are provided.

What is claimed is: 
     
         1 . A method for migrating virtual desktop sessions in a sticky session environment, comprising:
 selecting, by a load balancer, a first server to service a plurality of requests sent by a client;   determining, by the load balancer, that session data is associated with the plurality of requests;   selecting, by the load balancer, a second server to store the session data;   causing, by the load balancer, the first server to initiate a transmission of the session data to the second server; and   determining that the transmission of the session data was successful.   
     
     
         2 . The method of  claim 1 , wherein the load balancer comprises a reverse proxy. 
     
     
         3 . The method of  claim 1 , wherein the load balancer is configured to forward individual ones of the plurality of requests to the first server in response to at least one of:
 determining that an identifier associated with the session data indicates that the session data is associated with the first server, or determining that a cookie indicates that the first server is associated with the plurality of requests.   
     
     
         4 . The method of  claim 1 , further comprising:
 determining whether a load-related event has occurred.   
     
     
         5 . The method of  claim 4 , further comprising:
 in response to determining that the load-related event has not occurred:
 forwarding, to the first server, a request sent by the client. 
   
     
     
         6 . The method of  claim 4 , further comprising:
 in response to determining that the load-related event has occurred:
 updating an identifier associated with the session data to indicate that the session data is associated with the second server; and 
 forwarding, by the load balancer and to the second server, a request sent by the client. 
   
     
     
         7 . The method of  claim 1 , wherein at least one of the plurality of requests comprises a cookie that identifies at least one of: the first server, or the second server. 
     
     
         8 . The method of  claim 1 , further comprising:
 wherein determining that the transmission of the session data was successful comprises:
 receiving, by the load balancer, a positive acknowledgement sent by the first server indicating that the transmission of the session data is successfully completed. 
   
     
     
         9 . The method of  claim 1 , wherein the plurality of requests comprise requests for a remote desktop service; and wherein the session data comprises data associated with the remote desktop service providing a session to the client. 
     
     
         10 . A system for migrating virtual desktop sessions in a sticky session environment, comprising:
 a data store;   a load balancer in communication with the data store, the load balancer being configured to at least:
 select a first server to service a plurality of requests sent by a client; 
 determine that session data is associated with the plurality of requests; 
 select a second server to store the session data; 
 cause the first server to initiate a transmission of the session data to the second server; and 
 determine that the transmission of the session data was successful. 
   
     
     
         11 . The system of  claim 10 , wherein the load balancer is configured to forward individual ones of the plurality of requests to the first server in response to at least one of: determining that an identifier associated with the session data indicates that the session data is associated with the first server, or determining that a cookie indicates that the first server is associated with the plurality of requests. 
     
     
         12 . The system of  claim 10 , further comprising:
 in response to determining that a load-related event has occurred:
 update an identifier associated with the session data to indicate that the session data is associated with the second server; and 
 forward, to the second server, a request sent by the client. 
   
     
     
         13 . The system of  claim 10 , wherein at least one of the plurality of requests comprises a cookie that identifies at least one of: the first server, or the second server. 
     
     
         14 . The system of  claim 10 , wherein determining that the transmission of the session data was successful comprises:
 wherein the load balancer is further configured to:
 receive a positive acknowledgement sent by the first server indicating that the transmission of the session data is successfully completed. 
   
     
     
         15 . The system of  claim 10 , wherein the plurality of requests comprise requests for a remote desktop service; and wherein the session data comprises data associated with the remote desktop service providing a session to the client. 
     
     
         16 . A non-transitory computer-readable medium storing instructions that when executed by a computer system, cause the computer system to at least:
 select a first server to service a plurality of requests sent by a client;   determine that session data is associated with the plurality of requests;   select a second server to store the session data;   cause the first server to initiate a transmission of the session data to the second server; and   determine that the transmission of the session data was successful.   
     
     
         17 . The non-transitory computer-readable medium of  claim 16 , wherein the instructions further cause the computer system to:
 in response to determining that a load-related event has occurred:
 update an identifier associated with the session data to indicate that the session data is associated with the second server; and 
 forward, to the second server, a request sent by the client. 
   
     
     
         18 . The non-transitory computer-readable medium of  claim 16 , wherein at least one of the plurality of requests comprises a cookie that identifies at least one of: the first server, or the second server. 
     
     
         19 . The non-transitory computer-readable medium of  claim 16 , wherein determining that the transmission of the session data was successful comprises:
 wherein the instructions further cause the computer system to:
 receive a positive acknowledgement sent by the first server indicating that the transmission of the session data is successfully completed. 
   
     
     
         20 . The non-transitory computer-readable medium of  claim 16 , wherein the plurality of requests comprise requests for a remote desktop service; and wherein the session data comprises data associated with the remote desktop service providing a session to the client.