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

getLastError does not wait for replication on mongos v3.0 with mongod v3.2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.2.0-rc3
    • Fix Version/s: 3.2.0-rc4
    • Component/s: Replication, Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      Run jstests/rename.js with everything in v3.2 except for mongos (in v3.0)

      Show
      Run jstests/rename.js with everything in v3.2 except for mongos (in v3.0)
    • Sprint:
      Sharding D (12/11/15)

      Description

      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') } }
      

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: