[DOCS-5477] Document that 2dsphere indexes will be implicitly upgraded during the resync of 2.6/3.0 Created: 20/May/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Alexander Komyagin Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

2.6/3.0


Issue Links:
Related
Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

If a 2.4 node with 2dsphere indexes is upgraded to 2.6/3.0, the indexes will have an implicit version 1. However, a resync of the node (or sync of a new node) will implicitly recreate the index with explicit version 2.

This shouldn't be a big issue aside from possible (but unlikely) differences in behavior between replica set nodes. Once SERVER-13875 is fixed, sharded clusters should handle this well.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:50:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.