[DOCS-1205] Procedure on "Change Hostnames in a Replica Set" has an error Created: 07/Mar/13 Updated: 13/Sep/13 Resolved: 11/Sep/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Thomas Rueckstiess | 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: | 10 years, 23 weeks ago | ||||
| Description |
|
At http://docs.mongodb.org/manual/tutorial/change-hostnames-in-a-replica-set/#changing-hostnames-while-maintaining-the-replica-set-s-availability, there is an error in step 5. It doesn't make sense to start up the original primary (it's not needed anymore). I replaced the steps 3-5 with the following for a customer: ...
... Note how step 4 became the new step 5 and the replacement node should be started before the config change to not get errors about it being unreachable. I think step 1d. should also be changed as the secondary is not always at position 1 in the array. I would make this clearer. Something like "If the old node was at position 1, you would run: ...". |
| Comments |
| Comment by auto [ 11/Sep/13 ] |
|
Author: {u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |
| Comment by auto [ 11/Sep/13 ] |
|
Author: {u'username': u'bgrabar', u'name': u'Bob Grabar', u'email': u'bob.grabar@10gen.com'}Message: Signed-off-by: Sam Kleinman <samk@10gen.com> |