[SERVER-3935] mixing 1.8.3 and 2.0.0 in a replica set will cause 1.8.3 cannot use it's indexes Created: 23/Sep/11 Updated: 29/Feb/12 Resolved: 24/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Replication |
| Affects Version/s: | 1.8.3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Liu Qishuai | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | indexing | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
1. set up a new replica set on a 2.0.0 server |
| Comments |
| Comment by Liu Qishuai [ 26/Sep/11 ] |
|
The index is described as {v: 1}in system.indexes, but actually the index data is stored in old version. There is no assertion about index version in mongod <= 1.8.2, so it can correctly use the index. |
| Comment by Eliot Horowitz (Inactive) [ 25/Sep/11 ] |
|
1.8.2 will assert if a v1 index is used. |
| Comment by Liu Qishuai [ 25/Sep/11 ] |
|
I don't think it's expected. The 1.8.2 server can use the fake v1 index correctly, but 1.8.3 can't. |
| Comment by Eliot Horowitz (Inactive) [ 24/Sep/11 ] |
|
This is expected. See upgrade section in release notes: |