[SERVER-25971] Test performing ops against a 3.4 sharded cluster where the shards don't have a shardIdentity doc Created: 06/Sep/16  Updated: 19/Nov/16  Resolved: 19/Sep/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.3.14

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Esha Maharishi (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-24527 add test to ensure shard undergoes sh... Closed
related to SERVER-26083 create library of basic ops that can ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2016-09-19, Sharding 2016-10-10
Participants:

 Description   

During the 3.2->3.4 upgrade process there can exist a period of time where the shards are all v3.4, but the config server has yet to upsert a shardIdentity docuument on to the shards. We should verify that nothing goes wrong in that situation by writing a jstest that performs a variety of operations (CRUD, aggregate, mapReduce, findAndModify, distinct, count, group, etc) against a sharded cluster setup without shardIdentity documents.



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

Author:

{u'name': u'Esha Maharishi', u'email': u'esha.maharishi@mongodb.com'}

Message: SERVER-25971 Test performing ops against a 3.4 sharded cluster where the shards don't have a shardIdentity doc
Branch: master
https://github.com/mongodb/mongo/commit/71c222f029dbd9c8b73d8a2e5cc1be9f00a8675e

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