[SERVER-34430] Don't drop database from old primary shard after movePrimary Created: 12/Apr/18  Updated: 29/Oct/23  Resolved: 12/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.3
Fix Version/s: 3.7.4

Type: Bug 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
Operating System: ALL
Sprint: Sharding 2018-04-23
Participants:

 Description   

We should just drop the unsharded collections that were moved; there is no need to drop the whole database (and anyway, we only do that if there were no sharded collections), particularly since once unsharded collections are tracked as sharded collections with one chunk, it will be incorrect to drop the database.

Changing the FCV 4.0 protocol to not drop the database will prevent us from having to change the protocol in a later release (and therefore handle upgrade/downgrade and mixed-version clusters in that release).



 Comments   
Comment by Githook User [ 12/Apr/18 ]

Author:

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

Message: SERVER-34430 Don't drop database from old primary shard after movePrimary
Branch: master
https://github.com/mongodb/mongo/commit/ad12210e7d8c4c7777485039337ffa0d46b93086

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