[SERVER-30255] add safe secondary reads targeted tests for drop/recreate Created: 21/Jul/17  Updated: 30/Oct/23  Resolved: 24/Jul/17

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.10
Fix Version/s: 3.5.11

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-07-31
Participants:

 Description   

Essentially the same format as the other safe secondary reads tests, but
this one has 4 drop/recreate scenarios that it puts each command
through:

  • dropRecreateAsUnshardedOnSameShard
  • dropRecreateAsShardedOnSameShard
  • dropRecreateAsUnshardedOnDifferentShard
  • dropRecreateAsShardedOnDifferentShard

There is a subtle relationship between shard versioning and using UUIDs,
because epochs are a pseudo-UUID that exist only for sharded
collections.

I see this as part testing, part documentation of our current
drop/recreate behavior, which is sans UUIDs.



 Comments   
Comment by Githook User [ 24/Jul/17 ]

Author:

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

Message: SERVER-30255 fix lint
Branch: master
https://github.com/mongodb/mongo/commit/c1614b0819d525019de03eb961bd17ee0d3b7ee9

Comment by Githook User [ 24/Jul/17 ]

Author:

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

Message: SERVER-30255 add safe secondary reads targeted tests for drop/recreate
Branch: master
https://github.com/mongodb/mongo/commit/e4214d1761b34eb62a287b70f3539afad43e168f

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