Dropping Unused Collections in fb-mongod
Overview
This is part of fb-mongod decommissioning milestones.
On Feb 25th, 2021 we have revoked Read / Write access to unused or orphan collections residing in fb-mongod. As we've observed no regression happening for more than a month since access revocation, we'll be moving to the next step of dropping those collections from the database.
Plan
- April 7th, 2021 : Collection drop activity started from 4pm UTC+7
- List of collections to be dropped are available in this document (excluding rows that are highlighted red)
- Collection drop script can be viewed in this PR
- Drop script will be run one by one (currently a total of 88 collections are planned to be dropped).
- There will be no archival done from our end for the collections to be dropped
What do you need to do ?
- If for some reason you don't want a specific collection to be dropped despite them being unused (e.g. : you want to archive the contents of your data first), please let us know by April 5th EoD at the latest. Provide information on :
- your team's slack handle (will be committed as owner if it's an orphan collection)
- collection name(s) that you wish to retain
- until when should it be retained (please give a date)
- Otherwise there should be no action needed from your end
Should you have any further questions / concerns, please let us know in #fb-mongod-decommissioning channel. Thanks !