-
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)
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
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-57407 Avoid taking ReplicationCoordinator mutex when deciding to gossip cluster times with external clients
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- related to
-
-
- Open
-
-
-
- Open
-
-
-
- Backlog
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-54939 Investigate secondary batching behavior in v4.4
-
- Closed
-
- mentioned in
-
Page Loading...