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

snapshot_cursor_commands_mongos.js shouldn't move same chunk twice during all shard reads set up

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • ALL
    • Sharding 2019-04-22
    • 32

    Description

      Before running the multiShardAllReads test case, snapshot_cursor_commands_mongos.js shards a collection, splits it at 4 and 8, moves the chunk containing 0 to shard0, 4 to shard1, and 7 to shard2, and asserts each shard owns one chunk by checking the config.chunks collection. The same chunk contains 4 and 7 though, so no chunk is guaranteed to end on shard1, but the test rarely fails because shard1 is almost always chosen as the primary shard, so the 3rd chunk that isn't moved will remain on it.

      Instead of relying on which shard is the primary without explicitly enforcing it, the test should be updated to move a different chunk to each shard instead of moving the same one twice.

      Attachments

        Activity

          People

            jack.mulrow@mongodb.com Jack Mulrow
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: