[DOCS-1484] 2.2 -> 2.4 upgrade instructions need to include requirement to remove v0 indexes from config server Created: 05/May/13 Updated: 05/May/13 Resolved: 05/May/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Zola | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: | |||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 10 years, 41 weeks, 3 days ago | ||||||||||||
| Description |
|
The list of warnings does not include checking to make sure that all of the indexes on the config server are V1 indexes. If the config servers were originally installed as r1.8.x, and the indexes were never upgraded, then one or more of the critical config server indexes can be v0 indexes. If one of the critical indexes is not a V1 index, then shard chunk splits will fail once the upgrade is complete. |