Skip to content

Commit 26cf7dd

Browse files
committed
nit
1 parent 9e21314 commit 26cf7dd

File tree

1 file changed

+1
-1
lines changed
  • docs/integrations/data-ingestion/clickpipes/mongodb

1 file changed

+1
-1
lines changed

docs/integrations/data-ingestion/clickpipes/mongodb/faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ For more examples, see our [Working with JSON guide](./quickstart).
5252

5353
### How do I handle `resume of change stream was not possible, as the resume point may no longer be in the oplog.` error? {#resume-point-may-no-longer-be-in-the-oplog-error}
5454

55-
This error typically occurs when the oplog is truncated and ClickPipe is unable to resume the change stream at the expected point. To resolve this issue, [resync the ClickPipe](./resync.md). To avoid this issue from recurring, we recommend increasing the oplog retention period. See instructions for [MongoDB Atlas](./source/atlas#enable-oplog-retention), [self-managed MongoDB](./source/generic#enable-oplog-retention), or [Amazon DocumentDB](./source/docdb##configure-change-stream-log-retention).
55+
This error typically occurs when the oplog is truncated and ClickPipe is unable to resume the change stream at the expected point. To resolve this issue, [resync the ClickPipe](./resync.md). To avoid this issue from recurring, we recommend increasing the oplog retention period. See instructions for [MongoDB Atlas](./source/atlas#enable-oplog-retention), [self-managed MongoDB](./source/generic#enable-oplog-retention), or [Amazon DocumentDB](./source/docdb#configure-change-stream-log-retention).
5656

5757
### How is replication managed? {#how-is-replication-managed}
5858

0 commit comments

Comments
 (0)