[SERVER-1018] reIndex on master fails to create indexes on slave Created: 13/Apr/10 Updated: 12/Jul/16 Resolved: 11/May/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 1.4.0 |
| Fix Version/s: | 1.5.2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kristina Chodorow (Inactive) | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Slave log output: Tue Apr 13 14:41:19 repl: from host:10.211.143.79:27017 for buzzfeed.report } Actions: MASTER: ); }, , SLAVE: }, , MASTER: SLAVE: |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 08/Sep/10 ] |
|
Added a new case: |
| Comment by Swen Thümmler [ 08/Sep/10 ] |
|
master: }, , }, , master log: for test.foo } for test.foo , name: "_o_1" } for test.foo } for test.foo , name: "_o_1" } slave log: for test.foo } for test.foo , name: "_o_1" } |
| Comment by Swen Thümmler [ 08/Sep/10 ] |
|
This issue does not seem to be fixed for replication sets (I'm running 1.6.2 on linux). If I reIndex a collection on the current master, the collection looses all indexes on the slave (even the index on _id) |
| Comment by auto [ 11/May/10 ] |
|
Author: {'login': 'erh', 'name': 'Eliot Horowitz', 'email': 'eliot@10gen.com'}Message: don't use direct client for creating index on slave with reIndex |