-
Type:
Bug
-
Resolution: Works as Designed
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication
-
Execution Team 2024-04-29, Execution Team 2024-05-13, Execution Team 2024-05-27
Currently we have a check very early in the code to skip waiting for write concern completely if the command targets a non-replicated DB. I think this is incorrect for 2 reasons:
- We should honor j:1 write concerns even on the local db
- Even commands that target the local db can have replicated writes (eg using an agg $out stage into another db)
- depends on
-
SERVER-81782 Waiting for journalling is redundant with waiting for replication for replicated writes
-
- Closed
-