File tree Expand file tree Collapse file tree 1 file changed +14
-1
lines changed Expand file tree Collapse file tree 1 file changed +14
-1
lines changed Original file line number Diff line number Diff line change @@ -32,7 +32,7 @@ Change Stream Event Document Format
32
32
-----------------------------------
33
33
34
34
A change stream event document contains several fields that describe the
35
- change :
35
+ event :
36
36
37
37
* The top-level ``_id`` field is used as the :manual:`resume token
38
38
</changeStreams/#change-stream-resume>` which is
@@ -303,3 +303,16 @@ events, and broadcast changes after any collection data is updated.
303
303
304
304
database=example
305
305
copy.existing=true
306
+
307
+ How to Recover from An Invalid Resume Token
308
+ -------------------------------------------
309
+
310
+ If the event your Connector pauses or shuts down long enough for the Change Stream resume token
311
+ to expire from the :manual:`MongoDB Oplog </core/replica-set-oplog/>`_, you may encounter an error
312
+ that prevents you from starting up the Connector. If you encounter this
313
+ condition, you must delete the topic data referenced by
314
+ the ``offset.storage.topic`` setting if you are using Distributed Mode or the
315
+ file referenced by the ``offset.storage.file.filename`` setting (e.g.
316
+ ``/tmp/connect.offsets``) if you are using the Standalone mode. After you
317
+ delete the appropriate data, you should be able to start your Connector
318
+ workers and listen to the change stream.
You can’t perform that action at this time.
0 commit comments