[SERVER-3850] reIndex on primary does not propagate to secondaries Created: 14/Sep/11  Updated: 05/Oct/15  Resolved: 14/Sep/11

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

Type: Bug Priority: Major - P3
Reporter: Tony Hannan Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by SERVER-20757 Replica set secondaries stop replicat... Closed
Operating System: ALL
Participants:

 Description   

reIndex a

{v:0}

index on primary to

{v:1}

using db.foo.reIndex() command.
Viewing db.foo.getIndexes() on secondary still shows

{v:0}

.



 Comments   
Comment by Eliot Horowitz (Inactive) [ 14/Sep/11 ]

This is as intended.
reIndex is only supposed to be impact the db directly connected to.

Can you update docs if its not clear

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