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

add safe secondary reads targeted tests for drop/recreate

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 3.5.11
    • 3.5.10
    • Sharding
    • None
    • Fully Compatible
    • Sharding 2017-07-31

    Description

      Essentially the same format as the other safe secondary reads tests, but
      this one has 4 drop/recreate scenarios that it puts each command
      through:

      • dropRecreateAsUnshardedOnSameShard
      • dropRecreateAsShardedOnSameShard
      • dropRecreateAsUnshardedOnDifferentShard
      • dropRecreateAsShardedOnDifferentShard

      There is a subtle relationship between shard versioning and using UUIDs,
      because epochs are a pseudo-UUID that exist only for sharded
      collections.

      I see this as part testing, part documentation of our current
      drop/recreate behavior, which is sans UUIDs.

      Attachments

        Activity

          People

            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: