SERVER-129135Open
Secondary applying oplog can do more write IO than the primary and spiral into unrecoverable lag on IO-bound w:majority workloads
h2. Summary On a sustained, IO-bound `w:majority` write workload, a single secondary in a 3-node replica set can fall progressively behind, fail to recover, and go into maintenance mode (`REPL` log id 21126, "Too stale to catch up"). The other secondary keeps pace, so the majority commit point stays healthy and flow control never engages. Two questions: 1. Why does a secondary applying the oplog do more write IO than the primary that originated the writes? In healthy runs of this workload