[SERVER-3852] Initial sync of rs secondary copies old index version {v:0} although 2.0 release notes say otherwise Created: 14/Sep/11 Updated: 23/Sep/11 Resolved: 23/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Replication |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tony Hannan | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
http://www.mongodb.org/display/DOCS/Index+Versions says "Creation of a new replica set secondary from scratch (initial sync) will result in all its indexes being of {v:1}type". However, if the primary has a {v:0}index the new secondary after syncing will also have {v:0}for that index. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 23/Sep/11 ] |
| Comment by auto [ 19/Sep/11 ] |
|
Author: {u'login': u'TonyGen', u'name': u'Tony Hannan', u'email': u'tony@10gen.com'}Message: index from {v:0} index during initial sync |
| Comment by Eliot Horowitz (Inactive) [ 15/Sep/11 ] |
|
Can you write a test for this? |