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

mongos GLE does not work correctly if previous write was from a command

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Critical - P2 Critical - P2
    • 2.5.5
    • Affects Version/s: 2.5.4
    • Component/s: None
    • Labels:
      None
    • ALL
    • 0

      ... other than write commands.

      For example, if you run the 'create' command and call gle, w: 2, it never actually gets sent to the shards!

      We also need to confirm this on other commands that can do writes:

      • aggregate (with $out)
      • copydb
      • create
      • drop
      • dropDatabase
      • dropIndexes
      • findAndModify
      • mapReduce (with $out)
      • renameCollection

      And in this list, we need to make sure the writeConcern parameter works correctly:

      • createRole
      • createUser
      • dropAllRolesFromDatabase
      • dropAllUsersFromDatabase
      • dropRole
      • dropUser
      • grantPrivilegesToRole
      • grantRolesToRole
      • grantRolesToUser

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            randolph@mongodb.com Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: