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

Config servers need to always include $gleStats in their command responses if they are primary

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Sharding 9 (09/18/15), Sharding A (10/09/15)

      mongos uses $gleStats to work around commands that do not take write concern. For instance to create an index it runs createIndex, gets the optime after the insert from $gleStats, then uses that optime on a subsequent call to getLastError.

      SCCC config servers include $gleStats because they are always talked to over sharding-aware connections. We need to include $gleStats in command responses from CSRS config servers as well

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: