Skip to content

Commit 9a7f4d3

Browse files
authored
DOCS-15427 System Collection Limitations (#59)
* DOCS-15427 Adds System Collection limitation * DOCS-15427 Adds System Collection limitation * DOCS-15427 Fixes per Joe * DOCS-15427 Fixes per Joe
1 parent 7a9745b commit 9a7f4d3

File tree

1 file changed

+28
-1
lines changed

1 file changed

+28
-1
lines changed

source/reference/limitations.txt

Lines changed: 28 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,9 +107,36 @@ Multiple Clusters
107107
- Syncing one source cluster to many destination clusters is not
108108
supported.
109109

110+
System Collections
111+
------------------
112+
113+
{+c2c-product-name+} does not replicate :ref:`system collections
114+
<metadata-system-collections>` to the destination cluster.
115+
116+
If you issue a :dbcommand:`dropDatabase` command on the source cluster,
117+
this change is not directly applied on the destination cluster. Instead,
118+
{+c2c-product-name+} drops user collections and views in the database
119+
on the destination cluster, but it does not drop system collections
120+
on that database.
121+
122+
For example, on the destination cluster:
123+
124+
- The drop operation does not affect a user-created
125+
:data:`system.js <<database>.system.js>` collection.
126+
127+
- If you enable profiling, the :data:`system.profile
128+
<<database>.system.profile>` collection remains.
129+
130+
- If you create views on the source cluster and then drop the database,
131+
replicating the drop removes the views, but leaves an empty
132+
:data:`system.views <<database>.system.views>` collection.
133+
134+
In these cases, the replication of ``dropDatabase`` removes all user-created
135+
collections from the database, but leaves its system collections on the
136+
destination cluster.
110137

111138
.. contents:: On this page
112139
:local:
113140
:backlinks: none
114141
:depth: 1
115-
:class: singlecol
142+
:class: singlecol

0 commit comments

Comments
 (0)