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

prefix_shard_key.js depends on primary allocation to particular shards

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.6.7
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Linked BF Score:
      0

      Description

      When initializing a sharded cluster with a database, there's no guarantee which shard a primary will be initialized on without explicitly checking the "mapped" amount of data - this test should be fixed to explicitly move the primary to a particular shard before starting.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: