[DOCS-538] Tutorial on deploying a replica set doesn't include important diagnostic steps Created: 20/Sep/12 Updated: 30/Oct/23 Resolved: 03/Oct/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | William Zola | 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: | 11 years, 19 weeks, 6 days ago | ||||
| Description |
|
In the documentation page http://docs.mongodb.org/manual/tutorial/deploy-replica-set/ , there is no mention of the fact that users should verify connectivity between all three nodes in the replica set before beginning to configure replication. Given hosts A, B, and C, the following command needs to be run on each host: On Host A: Similarly, the same commands (verifying connectivity to the other two hosts) need to be run on hosts B and C. If these connections fail, initial synchronization will fail. |
| Comments |
| Comment by auto [ 04/Oct/12 ] |
|
Author: {u'date': u'2012-10-04T15:21:59-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |
| Comment by auto [ 04/Oct/12 ] |
|
Author: {u'date': u'2012-10-04T15:11:05-07:00', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: merge: |
| Comment by auto [ 04/Oct/12 ] |
|
Author: {u'date': u'2012-10-04T14:37:51-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |
| Comment by auto [ 04/Oct/12 ] |
|
Author: {u'date': u'2012-10-03T13:39:47-07:00', u'email': u'bob.grabar@10gen.com', u'name': u'Bob Grabar'}Message: |