[SERVER-44362] Remove track_unsharded_collections_create_collection.js and track_unsharded_collections_rename_collection.js Created: 01/Nov/19  Updated: 27/Oct/23  Resolved: 03/Mar/20

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

Type: Task Priority: Major - P3
Reporter: Janna Golden Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Gone away Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Sharding
Participants:
Linked BF Score: 11

 Description   

We should remove track_unsharded_collections_create_collection.js and track_unsharded_collections_rename_collection.js. The behavior to track an unsharded collection is under a feature flag and is not currently robust to config failovers. We do not plan to do the work to make it robust to config failovers and plan to remove this code from the server in the future anyway.



 Comments   
Comment by Esha Maharishi (Inactive) [ 03/Mar/20 ]

The tests have been removed.

Generated at Thu Feb 08 05:05:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.