-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
Write commands should fail with ok:0 when write concern is j:true and no journal is available.
{ "ok": 1, "n": 2, "writeConcernError": { "code": 2, "errmsg": "BadValue journaling not enabled" } }
getLastError returns the following in 2.6
{ "n": 0, "connectionId": 1, "writtenTo": null, "err": "nojournal", "ok": 0, "errmsg": "journaling not enabled", "code": 2 }
- duplicates
-
SERVER-12274 Fail-fast on invalid WriteConcern options in write commands
- Closed
- has to be done before
-
SERVER-9469 Implement mongod write commands misc functionality, addl.
- Closed
- related to
-
SERVER-12009 Broken Replication errors for getLastError
- Closed