[DOCS-6162] Comment on: "manual/core/sharded-cluster-shards.txt" Created: 08/Sep/15  Updated: 03/Nov/17  Resolved: 08/Sep/15

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Docs Collector User (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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


Participants:
Days since reply: 8 years, 23 weeks, 1 day ago

 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



 Comments   
Comment by Kay Kim (Inactive) [ 08/Sep/15 ]

Emailed reporter separately – the nomenclature corresponds to the field returned for each database in sh.status(). As the "primary" shard is the current working terminology, will not change, although things may change in the future.

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