[SERVER-12184] Write Commands not behaving like new getLastErrors Created: 21/Dec/13  Updated: 10/Dec/14  Resolved: 08/Jan/14

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

Type: Bug Priority: Major - P3
Reporter: Christian Amor Kvalheim Assignee: Greg Studer
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-12274 Fail-fast on invalid WriteConcern opt... Closed
Gantt Dependency
has to be done before SERVER-9469 Implement mongod write commands misc ... Closed
Related
related to SERVER-12009 Broken Replication errors for getLast... Closed
Operating System: ALL
Participants:

 Description   

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
}



 Comments   
Comment by Daniel Pasette (Inactive) [ 08/Jan/14 ]

duplicate: SERVER-12274

Generated at Thu Feb 08 03:27:50 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.