[DOCS-5406] Shouldn't add RS members individually when adding existing to monitoring Created: 10/May/15  Updated: 11/Jan/17  Resolved: 16/Dec/15

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

Type: Bug Priority: Major - P3
Reporter: Eric Sommer Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 8 years, 9 weeks ago

 Description   

In the procedure for Add Existing MongoDB Processes to Monitoring, is says:

"If you add processes from an environment that uses authentication, you must add each mongod instance separately and explicitly set the authentication credentials on each."

  1. This goes against the UI, which gives the user the ability to choose 'replica set' and add credentials for the set
  2. I asked some of the MMS engineers about this and was told that RS members with auth in use should indeed be added individually, but when I tried adding the 3 nodes as standalone nodes, it didn't work well – I ended up with a RS containing the 3 nodes plus a duplicate of one of the nodes as a standalone. When I import the RS as a RS, giving the primary, I get the desired result.

If this directive is truly correct, then a bug needs to opened for the UI to enforce it.



 Comments   
Comment by Bob Grabar [ 16/Dec/15 ]

https://docs.cloud.mongodb.com//tutorial/add-existing-mongodb-processes/ no longer says to add each auth-enabled mongod in a replica set separately.

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