[SERVER-26156] Additional tests for index version v=2 in a sharded cluster Created: 19/Sep/16  Updated: 19/Nov/16  Resolved: 27/Sep/16

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Querying
Affects Version/s: None
Fix Version/s: 3.3.15

Type: Task Priority: Major - P3
Reporter: Max Hirschhorn Assignee: Maria van Keulen
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-25156 Create index version V2 Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2016-10-10
Participants:

 Description   

Continued from SERVER-25156.

Test migrating a chunk for a collection with a v=2 index on it from a 3.4 mongod to a newly added 3.4 stand-alone mongod shard in featureCompatibilityVersion=3.2 succeeds and creates a v=2 index on the recipient shard.

Test migrating a chunk for a collection with a v=2 index on it from a 3.4 mongod to a newly added 3.2 stand-alone mongod shard fails.



 Comments   
Comment by Githook User [ 26/Sep/16 ]

Author:

{u'username': u'mvankeulen94', u'name': u'Maria van Keulen', u'email': u'maria.vankeulen@mongodb.com'}

Message: SERVER-26156 Add migration tests for collections with V2 indexes
Branch: master
https://github.com/mongodb/mongo/commit/aa9ea14a57181f098a32f24a734f2c81563bee5c

Comment by Tess Avitabile (Inactive) [ 19/Sep/16 ]

I agree that this cannot be prevented.

Comment by Max Hirschhorn [ 19/Sep/16 ]

Responding to this comment from SERVER-25156:

Be sure to test index creation while setMinVersion is being run on the cluster, to make sure we don't get V2 indexes on some nodes and V1 on others.

tess.avitabile, how could we not potentially end up with a v=2 index on one shard and a v=1 index on another shard? mongos doesn't resolve the default index version - each shard does for itself - so if running {setFeatureCompatibilityVersion: "3.4"} fails on some shard and then a user creates a new index, then two shards can end up with different index versions when the index is created.

Generated at Thu Feb 08 04:11:17 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.