Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-12184

Write Commands not behaving like new getLastErrors

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Operating System:
      ALL

      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
      }

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              greg_10gen Greg Studer
              Reporter:
              christkv Christian Amor Kvalheim
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: