[DOCS-15423] [C2C] Corner case for how dropDatabase is replicated Created: 17/Jun/22  Updated: 30/Oct/23  Resolved: 27/Jun/22

Status: Closed
Project: Documentation
Component/s: C2C, manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Task Priority: Minor - P4
Reporter: Lingzhi Deng Assignee: Dave Cuthbert (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 33 weeks, 5 days ago
Epic Link: DOCSP-22764

 Description   

Mongosync will only drop each individual views upon dropDatabase without dropping the system.views itself. This is because dropping system.views requires very special privileges that aren’t included in any built-in roles. This leaves a corner case where if a database with views is dropped on the source, the destination may still show the dropped database after commit with an empty system.views in that database. We believe this shouldn’t have any impact on the correctness of user data/application.

Similarly, if users turn on profiling on the destination (which could generate <db>.system.profile), mongosync will not be able drop the <db>.system.profile collection on the destination even if the source database is dropped.


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