Details
-
Bug
-
Resolution: Done
-
Major - P3
-
None
-
None
-
*Location*: http://docs.mongodb.org/manual/core/sharded-cluster-shards/#primary-shard
*User-Agent*: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
*Referrer*: http://docs.mongodb.org/manual/core/aggregation-pipeline-sharded-collections/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: core/sharded-cluster-shards
*Location*: http://docs.mongodb.org/manual/core/sharded-cluster-shards/#primary-shard *User-Agent*: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0 *Referrer*: http://docs.mongodb.org/manual/core/aggregation-pipeline-sharded-collections/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: core/sharded-cluster-shards
Description
Hey Guys,
I may be wrong and am not THAT fluent with sharding, but a have a question/suggestion.
Isn't the term primary a bit confusing here? I think you know what I mean. The term primary is also being used in the context of Replica Sets.
What I would suggest is to name it "default shard".
From my understanding the collections are going to be initially saved there and the shard is set to be default for the database. I may be wrong and misinterpret the documentation here, so if this is the case please let me know. Otherwise I would be happy to help!
Kind regards,
Vitalii Lysov