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

Write Commands not behaving like new getLastErrors

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      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
      }
      

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

              Created:
              Updated:
              Resolved: