[SERVER-39267] Guard opWriteConcernCounters behind flag Created: 29/Jan/19  Updated: 29/Oct/23  Resolved: 29/Jan/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.6.11, 4.0.6, 4.1.8

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Documented
is documented by DOCS-12403 Docs for SERVER-39267: Guard opWriteC... Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0, v3.6
Sprint: Repl 2019-02-11
Participants:

 Description   

The opWriteConcernCounters section of serverStatus should be disabled by default, with a flag to enable it, since it can have negative performance impact when SSL is disabled. (When SSL is enabled, other mutexes dominate.)



 Comments   
Comment by Githook User [ 01/Feb/19 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-39267 Guard opWriteConcernCounters behind flag

(cherry picked from commit 941c4fbab21029e3bbe577d953250116cd0e8533)
Branch: v3.6
https://github.com/mongodb/mongo/commit/60b21eaf808b8b21667eacc4838500dec2e339dc

Comment by Githook User [ 30/Jan/19 ]

Author:

{'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile'}

Message: SERVER-39267 Guard opWriteConcernCounters behind flag

(cherry picked from commit 941c4fbab21029e3bbe577d953250116cd0e8533)
Branch: v4.0
https://github.com/mongodb/mongo/commit/caa42a1f75a56c7643d0b68d3880444375ec42e3

Comment by Githook User [ 29/Jan/19 ]

Author:

{'username': 'tessavitabile', 'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile'}

Message: SERVER-39267 Guard opWriteConcernCounters behind flag
Branch: master
https://github.com/mongodb/mongo/commit/941c4fbab21029e3bbe577d953250116cd0e8533

Generated at Thu Feb 08 04:51:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.