Change operations are written to the oplog A single update/delete affecting multiple documents can result in many oplog entries The oplog is a capped collection (fixed size) Must have enough space to allow new secondaries to catch up after syncing from a primary, and cope with any applicable slaveDelay Secondaries query the primary's oplog and apply what they find All replica set members contain an oplog