[SERVER-34505] Dropping a database from a shard should clear the shard's in-memory cached database version Created: 16/Apr/18  Updated: 17/Apr/18  Resolved: 17/Apr/18

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

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

Issue Links:
Duplicate
duplicates SERVER-34431 Move DatabaseShardingState into its o... Closed
Sprint: Sharding 2018-04-23
Participants:

 Description   

This ensures that after a database drop + recreate on another shard, a stale mongos that attaches the old database's version discovers that the database has been recreated elsewhere.



 Comments   
Comment by Esha Maharishi (Inactive) [ 17/Apr/18 ]

Will be done as part of SERVER-34431.

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