[DOCS-3685] Primary shard of existing databases Created: 01/Jul/14  Updated: 04/Mar/15  Resolved: 01/Jul/14

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: v1.3.7

Type: Task Priority: Major - P3
Reporter: Joanna Cheng Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Participants:
Days since reply: 9 years, 33 weeks, 1 day ago

 Description   

http://docs.mongodb.org/manual/core/sharded-cluster-shards/

When you deploy a new sharded cluster, the “first” shard becomes the primary shard for all existing databases before enabling sharding. Databases created subsequently may reside on any shard in the cluster.

Let's say you have a server A with database foo (and lots of data), and servers B and C which do not have the database foo. You then set up a sharded cluster and addShards in this order: B, C, A. Once you enable sharding for foo, the primary is server A, even though it's not the first shard.

I tested this on 2.4.8, happy to do more testing if needed.



 Comments   
Comment by Githook User [ 01/Jul/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-3685: clarify where existing database live on a new sharded cluster
Branch: v2.4
https://github.com/mongodb/docs/commit/bbf1c8a114d67e35c0d5786b4a40d6e40392e039

Comment by Githook User [ 01/Jul/14 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-3685: clarify where existing database live on a new sharded cluster
Branch: master
https://github.com/mongodb/docs/commit/f57c86cc60d3a5fdde380edd5442a4dbca8c205a

Generated at Thu Feb 08 07:46:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.