Skip to content

Commit d396992

Browse files
Chris Choschmalliso
authored andcommitted
DOCSP-9860: document resume token failure (#11)
* DOCSP-9860: document resume token failure
1 parent f55efeb commit d396992

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

source/kafka-source.txt

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Change Stream Event Document Format
3232
-----------------------------------
3333

3434
A change stream event document contains several fields that describe the
35-
change:
35+
event:
3636

3737
* The top-level ``_id`` field is used as the :manual:`resume token
3838
</changeStreams/#change-stream-resume>` which is
@@ -303,3 +303,16 @@ events, and broadcast changes after any collection data is updated.
303303

304304
database=example
305305
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.

0 commit comments

Comments
 (0)