Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
None
-
None
-
single mongod --nojournal
-
ALL
Description
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 }
|
Attachments
Issue Links
- is related to
-
SERVER-12012 apply semantic write concern checks before writes applied
-
- Closed
-
-
SERVER-12184 Write Commands not behaving like new getLastErrors
-
- Closed
-