- 
    Type:Bug 
- 
    Resolution: Done
- 
    Priority:Major - P3 
- 
    None
- 
    Affects Version/s: 4.4.8, 5.0.2
- 
    Component/s: None
- 
        ALL
- 
        Repl 2021-09-20, Replication 2021-12-13, Replication 2021-12-27, Repl 2022-03-21, Repl 2022-04-04, Repl 2022-04-18, Repl 2022-05-02, Repl 2022-05-16, Repl 2022-05-30, Repl 2022-06-13, Repl 2022-06-27
- 
        (copied to CRM)
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
- 
        None
Insert 1M documents like so into a collection:
{x: 'x'.repeat(100), modified: false}
Then update like so:
db.c.updateMany({}, {$set: {modified: true}}, {writeConcern: {w: "majority"}})
Timings are as follows:
4.2.15: 56s 4.4.8: 82s 5.0.5: 86s
PMP profiling shows this seems to be accounted for by contention on the replication coordinator mutex in setMyLastAppliedOpTimeAndWallTimeForward.
- is related to
- 
                    SERVER-31694 17% throughput regression in insert workload -         
- Closed
 
-         
- 
                    SERVER-48522 Regression after mass deletion -         
- Closed
 
-         
- 
                    SERVER-53667 High rate of journal flushes on secondary in 4.4 -         
- Closed
 
-         
- 
                    SERVER-57407 Avoid taking ReplicationCoordinator mutex when deciding to gossip cluster times with external clients -         
- Closed
 
-         
- 
                    SERVER-66809 Move BSON serialization out of the lock in prepareReplMetadata -         
- Closed
 
-         
- 
                    SERVER-66810 Pull expensive calls like _wakeReadyWaiters out of the replSetUpdatePosition inner loop -         
- Closed
 
-         
- related to
- 
                    SERVER-55606 Majority writes with j: false perform worse than j: true -         
- Open
 
-         
- 
                    SERVER-62193 Improve insert_vector secondary performance -         
- Open
 
-         
- 
                    SERVER-65725 Mutex stats counters can use relaxed mode atomics -         
- Backlog
 
-         
- 
                    SERVER-65054 Avoid slow insert batches blocking replication -         
- Closed
 
-         
- 
                    SERVER-65657 Reduce calls to the cappedInsertNotifier for the oplog -         
- Closed
 
-         
- 
                    SERVER-65671 Use _termShadow in updateTerm and processReplSetMetadata -         
- Closed
 
-         
- 
                    SERVER-65938 Collection haveCappedWaiters should check actual waiters, not potential waiters -         
- Closed
 
-         
- 
                    SERVER-66023 Do not constantly reset election and liveness timers -         
- Closed
 
-         
- 
                    SERVER-54939 Investigate secondary batching behavior in v4.4 -         
- Closed
 
-         
- mentioned in
- 
                    Page Loading...