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
Exercise 10: What modifications should be done to the Chandy–Lamport snapshot protocol so that it records a strongly consistent snapshot (i.e., all channel states are recorded empty).
A cut $C$ is strongly consistent if, for all sending events $e \in C$ to another process, we also have the receiving event $e' \in C$. When a process receives its "take snapshot" message from the monitor, it broadcasts it without saving its local state before (like in the original Chandy-Lamport algorithm). The process will record its local state and send it to the monitor only when it receives its last "take snapshot" message from the other processes. Since the channels are FIFO, the last message sent from the other processes is always a "take snapshot" message, so no other kinds of messages can come after any process has recorded its local state.
This discussion was converted from issue #10 on March 31, 2024 19:13.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Exercise 10: What modifications should be done to the Chandy–Lamport snapshot protocol so that it records a strongly consistent snapshot (i.e., all channel states are recorded empty).
Beta Was this translation helpful? Give feedback.
All reactions