[SERVER-14480] Syncing a new node should have the same indexes as the primary Created: 07/Jul/14  Updated: 10/Dec/14  Resolved: 14/Jul/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Daniel Coupal Assignee: Ramon Fernandez Marina
Resolution: Done Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Participants:

 Description   

When a user brings up a new node, it does expect it to look like the primary.
If the initial sync is done off another secondary and that secondary does not have all the indexes, then the new sync'ed node will be missing the same indexes.



 Comments   
Comment by Eric Milkie [ 14/Jul/14 ]

The replication system is designed to replicate all data exactly. (An exception to this is the buildIndexes configuration flag; such nodes with buildIndexes:false are never chosen as sync sources.)
Restarting a node in standalone mode and changing the replicated data (or changing metadata like indexes) is not supported.

Generated at Thu Feb 08 03:35:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.