Broken Replication errors for getLastError

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:
      single mongod --nojournal
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In 2.4.3 and 2.5.4 a getLastError with

      {j:true}

      on a single mongod with nojournal produces.

      {  n: 0,
  connectionId: 7,
  jnote: 'journaling not enabled on this server',
  err: 'nojournal',
  ok: 1 }

      But on 2.5.5 nightly it produces

      {  n: 0,
  connectionId: 7,
  writtenTo: null,
  err: 'nojournal',
  ok: 0,
  errmsg: 'journaling not enabled',
  code: 2 }

              Assignee:
              Unassigned
              Reporter:
              Christian Amor Kvalheim
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: