Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
None
-
None
-
Sharding
-
Fully Compatible
-
ALL
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.
Attachments
Issue Links
- duplicates
-
SERVER-21190 Bring back --nojournal for config servers
-
- Closed
-