Write Commands not behaving like new getLastErrors

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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
      }
      

              Assignee:
              Greg Studer (Inactive)
              Reporter:
              Christian Amor Kvalheim
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: