[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 |
||
| 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". Kind regards, |
| 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. |