[DOCS-1127] Comment on: "reference/command/shardingState.txt" Created: 14/Feb/13 Updated: 04/Mar/15 Resolved: 07/Mar/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.2 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Ed Costello | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 10 years, 49 weeks, 6 days ago |
| Description |
|
shardingState only returns 'true' if the mongod is the primary member in a replica set which is part of a shard. When invoked against a primary, shardingState returns a document like:
but when invoked against a SECONDARY member, shardingState returns the document:
when invoked against a secondary member, even if it's part of a sharded cluster. When invoked against a config server, shardingState returns:
And when invoked against a mongos instance:
|
| Comments |
| Comment by Ed Costello [ 08/Mar/13 ] | |
|
Not sure where the "boolean" got in there.
(that is, you've run this against a primary but no collections have been sharded yet). | |
| Comment by auto [ 07/Mar/13 ] | |
|
Author: {u'date': u'2013-03-07T21:05:28Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: | |
| Comment by auto [ 07/Mar/13 ] | |
|
Author: {u'date': u'2013-03-07T21:05:28Z', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |