[SERVER-15766] prefix_shard_key.js depends on primary allocation to particular shards Created: 21/Oct/14  Updated: 02/Feb/15  Resolved: 18/Dec/14

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 2.6.7

Type: Bug Priority: Minor - P4
Reporter: Greg Studer Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
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.



 Comments   
Comment by Githook User [ 18/Dec/14 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-15766 prefix_shard_key.js depends on primary allocation to particular shards
Branch: v2.6
https://github.com/mongodb/mongo/commit/7983497cd7fdec7029f1638ab7d4309760dfba82

Generated at Thu Feb 08 03:38:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.