[SERVER-8587] Reindex needed after upgrade through replication? Created: 15/Feb/13  Updated: 15/Feb/13  Resolved: 15/Feb/13

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Replication
Affects Version/s: 2.2.2
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Jon Eisenstein Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

ReplicaSet upgraded from 1.6


Participants:

 Description   

After having completed an upgrade from 1.6 to 2.2 via launching new instances, adding them to the ReplicaSet and letting them update, and then removing the old instances, do I still need to reindex to get more performance? Or did the replication (versus upgrading the Mongo version on the same instance with the old data files) handle the newer and better index style already?

If I do have to re-index, can it be done without downtime?



 Comments   
Comment by Scott Hernandez (Inactive) [ 15/Feb/13 ]

If the new replicas did an initial sync, and had no data to start with, then they have already been updated to the latest index version and there is no need for a reIndex or repair/rebuild.

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