Distributed storage of state information and session recovery using state information
A method for storing session state data of a session between a system having a plurality of nodes and a client device includes delivering a service to the client device during a session identified or otherwise specified by a session identifier. The service is delivered by a first of the plurality of nodes in the system. During the session, at least a second node in the system is selected on which session state data associated with the session is to be saved. The second node is selected based on the session identifier such that another node in the system is able to locate the session state data when stored on the second node from the session identifier without contacting a centralized mechanism that specifies where session state data is stored. The session state data is saved to the second node that is selected.
1. An apparatus configured for use as a first node among a plurality of nodes for storing session state data of a session between a client device and the first node, the first node configured to:
deliver a service to the client device during the session and specified by a session identifier;
during the session, using the session identifier to uniquely identify and select, from among a plurality of other nodes at least a second node in the system on which session state data associated with the session is to be saved, such that another node in the system is able to resume the session after locating the session state data using the session identifier, and without contacting a centralized mechanism that specifies where session state data is stored; and
saving the session state data to the second node that is selected.
2. The apparatus of claim 1 , further configured to generate a hash of the session identifier, wherein selecting at least the second node includes mapping the hash of the session identifier to indices of the nodes in the system to identify the second node that is to be selected for storing the session state data.
3. The apparatus of claim 1 , wherein selecting at least a second node in the system on which the session state data is to be saved includes selecting a plurality of nodes in the system on which the session state is to be saved, a number of nodes in the plurality of nodes being based on a previously established system policy.
4. The apparatus of claim 2 , wherein the session identifier is a universally unique identifier (UUID) that is unique within the system for no more than a specified period of time.
5. The apparatus of claim 1 , wherein the session state data that is saved includes sufficient data to resume the session when another node other than the first node obtains the session state data from the second node and delivers the service to the client device upon resuming the session.
6. The apparatus of claim 1 , further configured to, subsequent to an interruption in delivery of the service from the first node to the client device:
receive a session resume request from the client device at a third node in the system, the session resume request including information allowing the third node to obtain the session identifier;
hash the session identifier;
identify the second node on which the session state data for the session is stored based on the hash of the session identifier;
obtain the session state data from the second node; and
use the session state data so that the third node is able to resume delivery of service to the client device.
7. The apparatus of claim 1 delivering adaptive bit rate (ABR) streaming content to the client device, each of the nodes of the system including an instance of a manifest manipulator delivering ABR manifests to the client device, wherein the service being delivered to the client device includes delivery of ABR streaming content to the client device.
8. The apparatus of claim 7 , operatively connected to the plurality of nodes, which are grouped into different clusters of nodes and wherein selecting the second node in the system on which the session state data associated with the session is to be saved further comprises selecting the second node based in part on a previously established system policy concerning those clusters of nodes in which session state data may be saved by the first node.
9. The apparatus of claim 1 , wherein the session state data has a shard count greater than or equal to one and wherein selecting at least a second node in the system on which the session state data is to be saved includes selecting a plurality of nodes in the system on which the session state is to be saved, each of the node is the plurality of nodes saving a different shard of the session state data.
10. The apparatus of claim 9 , wherein at least two different shards of the session state data are periodically saved at different time intervals.
11. The apparatus of claim 9 , wherein at least two different shards of the session state data have different times to live.