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

Operations that convey shard version information must include a minimum optime

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.9
    • Affects Version/s: 3.1.7
    • Component/s: Sharding
    • None
    • Fully Compatible
    • ALL
    • Hide

      Change the read preference in the CSRS catalog manager implementation to "secondary preferred" and run the sharding test suite.

      Show
      Change the read preference in the CSRS catalog manager implementation to "secondary preferred" and run the sharding test suite.
    • Sharding 8 08/28/15, Sharding 9 (09/18/15), Sharding A (10/09/15)
    • 0

      When a setShardVersion command, find command or write command that includes shard version information is sent to a shard server from another node (typically a mongos), it must also include the an optime on the config server no earlier than the earliest one in which that shard version information became available. Otherwise, a shard server refreshing its view of the sharding metadata from a secondary might read too-old metadata, and not see the new shard version.

            Assignee:
            spencer@mongodb.com Spencer Brody (Inactive)
            Reporter:
            schwerin@mongodb.com Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: