Chandy–Lamport algorithm

The Chandy–Lamport algorithm is a snapshot algorithm that is used in distributed systems for recording a consistent global state of an asynchronous system. It was developed by and named after Leslie Lamport and K. Mani Chandy.

History
According to Leslie Lamport's website, “The distributed snapshot algorithm described here came about when I visited Chandy, who was then at the University of Texas in Austin. He posed the problem to me over dinner, but we had both had too much wine to think about it right then. The next morning, in the shower, I came up with the solution. When I arrived at Chandy's office, he was waiting for me with the same solution.”

Definition
The assumptions of the algorithm are as follows:
 * There are no failures and all messages arrive intact and only once
 * The communication channels are unidirectional and FIFO ordered
 * There is a communication path between any two processes in the system
 * Any process may initiate the snapshot algorithm
 * The snapshot algorithm does not interfere with the normal execution of the processes
 * Each process in the system records its local state and the state of its incoming channels

The algorithm works using marker messages. Each process that wants to initiate a snapshot records its local state and sends a marker on each of its outgoing channels. All the other processes, upon receiving a marker, record their local state, the state of the channel from which the marker just came as empty, and send marker messages on all of their outgoing channels. If a process receives a marker after having recorded its local state, it records the state of the incoming channel from which the marker came as carrying all the messages received since it first recorded its local state.

Some of the assumptions of the algorithm can be facilitated using a more reliable communication protocol such as TCP/IP. The algorithm can be adapted so that there could be multiple snapshots occurring simultaneously.

Algorithm
The Chandy–Lamport algorithm works like this:


 * 1) The observer process (the process taking a snapshot):
 * 2) Saves its own local state
 * 3) Sends a snapshot request message bearing a snapshot token to all other processes
 * 4) A process receiving the snapshot token for the first time on any message:
 * 5) Sends the observer process its own saved state
 * 6) Attaches the snapshot token to all subsequent messages (to help propagate the snapshot token)
 * 7) When a process that has already received the snapshot token receives a message that does not bear the snapshot token, this process will forward that message to the observer process.  This message was obviously sent before the snapshot “cut off” (as it does not bear a snapshot token and thus must have come from before the snapshot token was sent out) and needs to be included in the snapshot.

From this, the observer builds up a complete snapshot: a saved state for each process and all messages “in the ether” are saved.