[DOCS-4263] Adding hosts for monitoring implies auto discovery / monitoring of shards which is not true Created: 29/Oct/14 Updated: 16/Mar/15 Resolved: 17/Nov/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Cloud Manager |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.14 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Anil Kumar | Assignee: | Bob Grabar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 9 years, 13 weeks, 2 days ago | ||||
| Description |
|
Page: http://mms.mongodb.com/help-classic/tutorial/add-hosts-to-monitoring/ The above listed help implicitly implies that in a sharded cluster with authentication enabled, just adding a mongos host will discover all the shards elements and monitor them successfully. This does not gel with the reality where the shard mongod needs to be edited explicitly update the authentication credentials on one of the nodes of each shard. |
| Comments |
| Comment by Githook User [ 17/Nov/14 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: |
| Comment by Bob Grabar [ 17/Nov/14 ] |
|
I've created this pull request: |