[SERVER-34505] Dropping a database from a shard should clear the shard's in-memory cached database version - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Task
Status: Closed
Priority: Major - P3
Resolution: Duplicate
Affects Version/s: None
Fix Version/s: None
Component/s: Sharding
Labels:
None

Sprint:
Sharding 2018-04-23

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.

Attachments

Issue Links

duplicates

SERVER-34431 Move DatabaseShardingState into its own map to correctly handle database versioning in face of drop/recreate

Closed

Activity

People

Assignee:: Esha Maharishi (Inactive)

Reporter:: Esha Maharishi (Inactive)

Participants:: Esha Maharishi

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: Apr 16 2018 07:57:30 PM UTC

Updated:: Apr 17 2018 07:17:54 PM UTC

Resolved:: Apr 17 2018 07:17:44 PM UTC