You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: config.yaml
+27-1Lines changed: 27 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -158,6 +158,18 @@ cloner:
158
158
# A collection of 1M docs will be split into 100 segments of 10k docs
159
159
segment_size_docs: 10000
160
160
161
+
# num_retries: How many times to retry failed operations (reads/writes)
162
+
# Default: 5
163
+
num_retries: 5
164
+
165
+
# retry_interval_ms: How long to wait (in ms) between retries
166
+
# Default: 1000
167
+
retry_interval_ms: 1000
168
+
169
+
# write_timeout_ms: Max time (in ms) for a single bulk write batch to complete
170
+
# Default: 30000
171
+
write_timeout_ms: 30000
172
+
161
173
# -----------------------------------------------
162
174
# Change Data Capture (CDC) Settings
163
175
# -----------------------------------------------
@@ -179,4 +191,18 @@ cdc:
179
191
# Increasing this value helps if you have a very high volume of changes on the source (DocumentDB) and your target (MongoDB) has plenty of CPU/IO capacity.
180
192
# It prevents the application from falling behind simply because it can't write fast enough.
181
193
# Resource Usage: Setting this too high can saturate the connections or CPU on your target MongoDB cluster, potentially slowing down other operations.
182
-
max_write_workers: 8
194
+
max_write_workers: 8
195
+
196
+
# num_retries: How many times to retry a failed batch (due to network/connection issues)
197
+
# before giving up and stopping the migration.
198
+
# Default: 10
199
+
num_retries: 10
200
+
201
+
# retry_interval_ms: How long to wait (in milliseconds) between retry attempts.
202
+
# Default: 1000 (1 second)
203
+
retry_interval_ms: 1000
204
+
205
+
# write_timeout_ms: The maximum time to wait for a BulkWrite operation to complete.
206
+
# If the network hangs, this ensures the worker doesn't freeze forever.
Copy file name to clipboardExpand all lines: faq.md
+11Lines changed: 11 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -231,6 +231,17 @@ While the architecture supports sharding, there are important caveats, particula
231
231
232
232
---
233
233
234
+
## Q: Can I migrate from a non sharded DocumentDB cluster to a sharded MongoDB cluster?
235
+
**A:** Yes, please note that docStreamer does not perform sharding setup operations (such as enableSharding or shardCollection). You must configure the sharding topology manually before starting the migration.
236
+
237
+
Recommended Workflow:
238
+
239
+
1. Pre-Create and Shard: Before starting the migration, manually create your target databases and collections, and enable sharding with your desired shard keys.
240
+
2. Start Migration: When docStreamer starts, it will detect that the collections already exist and skip the creation step.
241
+
3. Data Loading: The tool will insert data through the mongos router, allowing MongoDB to automatically distribute the documents across shards based on your pre-configured setup.
242
+
243
+
---
244
+
234
245
## Q: Are new databases and collections migrated to destination if they were created on source while docStreamer is running?
235
246
**A:** Yes. New collections and databases created while docStreamer is running (and while it is paused), will be detected and migrated.
0 commit comments