← Back to Labs

etcd Commit Path

Follow one etcd write from leader proposal to quorum commit, MVCC revision, watch delivery, and lagging follower recovery.

clientcontrol-plane writeTxn Put /registry/leases/search => node-7leaderRaft log and apply pathterm 91, commit index 1842202, waiting for proposalonly the leader may propose new history in this termfollower Aquorum partnermatched through index 1842202follower Blagging membermatched through index 1842202MVCC backendcommit index 1842202revision 481921 visiblecommitted log state becomes visible keyspace state herewatch clientordered event streamcontroller is caught up through rev 481921no snapshot transfer in flightproposalAppendEntriesquorum ack decides commitapplywatchsnapshot when old log is already compacted
Step 1 / 6A client sends one mutation to the current leader

etcd does not let every node invent new history. The client talks to the leader, because only the leader may place a new command into the Raft log for this term.

Commit index
1842202
Visible revision
481921 visible
Watch state
controller is caught up through rev 481921

Arrow keys to navigate · R to reset

Tap dots to jump to any step

Read the full article →Take the quiz →