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

Operations that convey shard version information must include a minimum optime

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.1.7
    • Fix Version/s: 3.1.9
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      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.
    • Sprint:
      Sharding 8 08/28/15, Sharding 9 (09/18/15), Sharding A (10/09/15)
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved: