[DOCS-4138] Add a note to use the same user to start the secondary as a standalone instance in the document for replica set maintenance Created: 07/Oct/14 Updated: 26/Sep/17 Resolved: 13/Oct/14 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | v1.3.12 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Linda Qin | Assignee: | Sam Kleinman (Inactive) |
| 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, 18 weeks, 2 days ago | ||||
| Description |
|
In the document Perform Maintenance on Replica Set Members, there is a step to start the secondary as a standalone on a different port. It would be nice if we can add a note that we should use the same user (that we used to start this node as a member of the replica set) to start the secondary as a standalone instance. Otherwise, if the maintenance task creates new data files, the data files may be owned by a different user. When we start the mongod as a member of the replica set, it may have issue to open those data files. This could happen when we try to create a new index, or to change the size of system.profile collection, etc, during the maintenance. |
| Comments |
| Comment by Githook User [ 13/Oct/14 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |