[DOCS-16512] Chained Replication caveats are unclear Created: 27/Nov/23 Updated: 08/Jan/24 Resolved: 28/Nov/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_[20240108] |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Michael Struening | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| URL(s): | https://www.mongodb.com/docs/manual/tutorial/manage-chained-replication/
https://www.mongodb.com/docs/manual/reference/command/replSetSyncFrom/#mongodb-dbcommand-dbcmd.replSetSyncFrom |
| Participants: | |
| Days since reply: | 10 weeks, 2 days ago |
| Description |
|
Good day, I have a case with a customer that involved Chained Replication. As I looked through the various documentation articles, I found a paragraph that seemed to conflict with itself:
There's also no indication of what node a given secondary will use when Chained Replication is disabled. I confirmed with the expert team that disabling chained replication results in all nodes replicating from the Primary node, and that you can still move it via replSetSyncFrom though if THAT node becomes unavailable, the secondary in question will move to the primary for synch sourcing:
Can we update the linked documentation pages (and anything connected that I may have missed) to indicate: # Disabling Chained Replication will result in nodes synching from the Primary (and the resulting load on that Primary)
|
| Comments |
| Comment by Jocelyn Mendez [ 28/Nov/23 ] |
|
Closing due to site rank being 3428. |