-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 3.2.0-rc3
-
Component/s: Replication, Sharding
-
None
-
Fully Compatible
-
ALL
-
-
Sharding D (12/11/15)
getLastError on v3.0 mongos does not appear to wait for write concern after a command that writes (insert, update, remove, create. rename, findAndModify, etc).
This appears to be caused by a change in the format of $gleStats in command response from
{ ok: 1.0, $gleStats: { lastOpTime: Timestamp 1448055284000|3, electionId: ObjectId('564f91f159f75549f0be5a83') } }
in v3.0 to
{ ok: 1.0, $gleStats: { lastOpTime: { ts: Timestamp 1448054994000|4, t: 2 }, electionId: ObjectId('564f909b0000000000000002') } }
- is related to
-
SERVER-21586 Investigate v3.0 mongos and v3.2 cluster compatibility issues in jstests/sharding
-
- Closed
-
-
-
- Closed
-