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

Write tests to ensure that operations using DBDirectClient handle shard versioning properly

    • Type: Icon: Improvement Improvement
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.2.1, 3.3.0
    • Affects Version/s: None
    • Component/s: Sharding
    • Fully Compatible
    • Sharding C (11/20/15), Sharding D (12/11/15), Sharding E (01/08/16)

      Since 2f7b99c780cfdce94b2888ddc8e078536af459a6 we disable all shard version checking while in DBDirectClient. We need to make sure that all operations that use DBDirectClient while operating on sharded collections (maybe just map-reduce?) properly do their own shard versioning handling and weren't relying on shard version checking to happen via DBDirectClient.

      As for what the test could look like, I was thinking of something along the line of doing a map-reduce on a stale mongos right after a chunk migration and purposefully creating some orphaned data on the former chunk owner and making sure the map reduce sees the proper data

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

              Created:
              Updated:
              Resolved: