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

getLastError with write concern may return early after call to createIndexes on same connection

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Minor - P4 Minor - P4
    • None
    • 3.2.9, 3.3.11
    • Sharding
    • None
    • Sharding
    • ALL
    • Sharding 2016-08-29
    • 0

    Description

      The code for tracking the optime of the last write operation, specifically when that operation was index creation, has a bug on mongos that is exposed when the createIndexes command was forwarded to one or more shards using a new connection. Specifically, sometimes mongos will mistakenly believe that the optime of the createIndexes operation one or more shards was (0|0), causing waits for write concern >= w:2 to return too early.

      Attachments

        Activity

          People

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            schwerin@mongodb.com Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: