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

Shard name from a single node mongod not used as shard index in getSerializedCluster concurrency suite file cluster.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.4.0-rc4
    • 3.4.1, 3.5.1
    • Testing Infrastructure
    • None
    • Fully Compatible
    • ALL
    • TIG 2016-12-12

    Description

      The shard name, when using a standalone mongod, instead of a replica set is use an index into the shards in getSerializedCluster. The index used are 'shard0', 'shard1',... It should be based on the return from the invocation to ShardingTest as shard.shardName, i.e., 'shard0000'.

      Attachments

        Activity

          People

            jonathan.abrahams Jonathan Abrahams
            jonathan.abrahams Jonathan Abrahams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: