[SERVER-22500] Do not require journaling for config servers in tests Created: 05/Feb/16  Updated: 06/Dec/22  Resolved: 08/Mar/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Scott Hernandez (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-21190 Bring back --nojournal for config ser... Closed
Assigned Teams:
Sharding
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Due to a bug in replication and the interaction of WriteConcern::Majority and journalling we did not move the commit point forward, and had issues with ReadConcern::Majority. Now that that is fixed, we should:

  • Look at running config server in sharded js tests without journaling
  • If that goes well, evaluate if the overhead of checkpoints over journaling in WT is significant enough a performance penalty to disallow supporting it.

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