Skip to content

Commit e2dc6d0

Browse files
MOLT May docs work (#23402)
* initial commit * fixed skipped_unmigratable_tables format
1 parent b8b0c16 commit e2dc6d0

6 files changed

Lines changed: 37 additions & 36 deletions

File tree

src/current/_includes/molt/delta-all-sources.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -374,15 +374,15 @@ MOLT Fetch captures a consistent point-in-time checkpoint at the start of the da
374374
You should see periodic primary keepalive messages:
375375

376376
~~~
377-
DEBUG [Aug 25 14:38:10] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:09.556773 -0500 CDT" ServerWALEnd=0/49913A58
378-
DEBUG [Aug 25 14:38:15] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:14.556836 -0500 CDT" ServerWALEnd=0/49913E60
377+
DEBUG [2025-08-25T14:38:10-05:00] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:09.556773 -0500 CDT" ServerWALEnd=0/49913A58
378+
DEBUG [2025-08-25T14:38:15-05:00] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:14.556836 -0500 CDT" ServerWALEnd=0/49913E60
379379
~~~
380380

381381
When rows are successfully replicated, you should see debug output like the following:
382382

383383
~~~
384-
DEBUG [Aug 25 14:40:02] upserted rows conflicts=0 duration=7.855333ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
385-
DEBUG [Aug 25 14:40:02] progressed to LSN: 0/49915DD0
384+
DEBUG [2025-08-25T14:40:02-05:00] upserted rows conflicts=0 duration=7.855333ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
385+
DEBUG [2025-08-25T14:40:02-05:00] progressed to LSN: 0/49915DD0
386386
~~~
387387
</section>
388388

@@ -392,30 +392,30 @@ MOLT Fetch captures a consistent point-in-time checkpoint at the start of the da
392392
~~~
393393
[2025/08/25 15:29:09] [info] binlogsyncer.go:463 begin to sync binlog from GTID set 77263736-7899-11f0-81a5-0242ac120002:1-38
394394
[2025/08/25 15:29:09] [info] binlogsyncer.go:409 Connected to mysql 8.0.43 server
395-
INFO [Aug 25 15:29:09] connected to MySQL version 8.0.43
395+
INFO [2025-08-25T15:29:09-05:00] connected to MySQL version 8.0.43
396396
~~~
397397

398398
When rows are successfully replicated, you should see debug output like the following:
399399

400400
~~~
401-
DEBUG [Aug 25 15:29:38] upserted rows conflicts=0 duration=1.801ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
402-
DEBUG [Aug 25 15:29:38] progressed to consistent point: 77263736-7899-11f0-81a5-0242ac120002:1-39
401+
DEBUG [2025-08-25T15:29:38-05:00] upserted rows conflicts=0 duration=1.801ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
402+
DEBUG [2025-08-25T15:29:38-05:00] progressed to consistent point: 77263736-7899-11f0-81a5-0242ac120002:1-39
403403
~~~
404404
</section>
405405

406406
<section class="filter-content" markdown="1" data-scope="oracle">
407407
When transactions are read from the Oracle source, you should see registered transaction IDs (XIDs):
408408

409409
~~~
410-
DEBUG [Jul 3 15:55:12] registered xid 0f001f0040060000
411-
DEBUG [Jul 3 15:55:12] registered xid 0b001f00bb090000
410+
DEBUG [2025-07-03T15:55:12-05:00] registered xid 0f001f0040060000
411+
DEBUG [2025-07-03T15:55:12-05:00] registered xid 0b001f00bb090000
412412
~~~
413413

414414
When rows are successfully replicated, you should see debug output like the following:
415415

416416
~~~
417-
DEBUG [Jul 3 15:55:12] upserted rows conflicts=0 duration=2.620009ms proposed=13 target="\"molt_movies\".\"USERS\".\"CUSTOMER_CONTACT\"" upserted=13
418-
DEBUG [Jul 3 15:55:12] upserted rows conflicts=0 duration=2.212807ms proposed=16 target="\"molt_movies\".\"USERS\".\"CUSTOMER_DEVICE\"" upserted=16
417+
DEBUG [2025-07-03T15:55:12-05:00] upserted rows conflicts=0 duration=2.620009ms proposed=13 target="\"molt_movies\".\"USERS\".\"CUSTOMER_CONTACT\"" upserted=13
418+
DEBUG [2025-07-03T15:55:12-05:00] upserted rows conflicts=0 duration=2.212807ms proposed=16 target="\"molt_movies\".\"USERS\".\"CUSTOMER_DEVICE\"" upserted=16
419419
~~~
420420
</section>
421421

src/current/_includes/molt/fetch-data-load-output.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -88,13 +88,13 @@
8888

8989
<section class="filter-content" markdown="1" data-scope="postgres">
9090
~~~ json
91-
{"level":"info","type":"summary","fetch_id":"f5cb422f-4bb4-4bbd-b2ae-08c4d00d1e7c","num_tables":3,"tables":["migration_schema.employees","migration_schema.payments","migration_schema.payments"],"cdc_cursor":"0/3F41E40","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:30:37-04:00","message":"fetch complete"}
91+
{"level":"info","type":"summary","fetch_id":"f5cb422f-4bb4-4bbd-b2ae-08c4d00d1e7c","num_tables":3,"tables":["migration_schema.employees","migration_schema.payments","migration_schema.payments"],"skipped_unmigratable_tables":[],"cdc_cursor":"0/3F41E40","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:30:37-04:00","message":"fetch complete"}
9292
~~~
9393
</section>
9494

9595
<section class="filter-content" markdown="1" data-scope="mysql">
9696
~~~ json
97-
{"level":"info","type":"summary","fetch_id":"f5cb422f-4bb4-4bbd-b2ae-08c4d00d1e7c","num_tables":3,"tables":["public.employees","public.payments","public.payments"],"cdc_cursor":"4c658ae6-e8ad-11ef-8449-0242ac140006:1-29","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:30:37-04:00","message":"fetch complete"}
97+
{"level":"info","type":"summary","fetch_id":"f5cb422f-4bb4-4bbd-b2ae-08c4d00d1e7c","num_tables":3,"tables":["public.employees","public.payments","public.payments"],"skipped_unmigratable_tables":[],"cdc_cursor":"4c658ae6-e8ad-11ef-8449-0242ac140006:1-29","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:30:37-04:00","message":"fetch complete"}
9898
~~~
9999

100100
{% if page.name contains "delta" %}
@@ -109,7 +109,7 @@
109109

110110
<section class="filter-content" markdown="1" data-scope="oracle">
111111
~~~ json
112-
{"level":"info","type":"summary","fetch_id":"f5cb422f-4bb4-4bbd-b2ae-08c4d00d1e7c","num_tables":3,"tables":["migration_schema.employees","migration_schema.payments","migration_schema.payments"],"cdc_cursor":"backfillFromSCN=26685444,scn=26685786","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:30:37-04:00","message":"fetch complete"}
112+
{"level":"info","type":"summary","fetch_id":"f5cb422f-4bb4-4bbd-b2ae-08c4d00d1e7c","num_tables":3,"tables":["migration_schema.employees","migration_schema.payments","migration_schema.payments"],"skipped_unmigratable_tables":[],"cdc_cursor":"backfillFromSCN=26685444,scn=26685786","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:30:37-04:00","message":"fetch complete"}
113113
~~~
114114

115115
{% if page.name contains "delta" %}

src/current/_includes/molt/phased-delta-failback-all-sources.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -388,15 +388,15 @@ Verify that Replicator is processing changes successfully. To do so, check the M
388388
You should see periodic primary keepalive messages:
389389
390390
~~~
391-
DEBUG [Aug 25 14:38:10] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:09.556773 -0500 CDT" ServerWALEnd=0/49913A58
392-
DEBUG [Aug 25 14:38:15] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:14.556836 -0500 CDT" ServerWALEnd=0/49913E60
391+
DEBUG [2025-08-25T14:38:10-05:00] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:09.556773 -0500 CDT" ServerWALEnd=0/49913A58
392+
DEBUG [2025-08-25T14:38:15-05:00] primary keepalive received ReplyRequested=false ServerTime="2025-08-25 14:38:14.556836 -0500 CDT" ServerWALEnd=0/49913E60
393393
~~~
394394
395395
When rows are successfully replicated, you should see debug output like the following:
396396
397397
~~~
398-
DEBUG [Aug 25 14:40:02] upserted rows conflicts=0 duration=7.855333ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
399-
DEBUG [Aug 25 14:40:02] progressed to LSN: 0/49915DD0
398+
DEBUG [2025-08-25T14:40:02-05:00] upserted rows conflicts=0 duration=7.855333ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
399+
DEBUG [2025-08-25T14:40:02-05:00] progressed to LSN: 0/49915DD0
400400
~~~
401401
</section>
402402
@@ -406,30 +406,30 @@ You should see binlog syncer connection and row processing:
406406
~~~
407407
[2025/08/25 15:29:09] [info] binlogsyncer.go:463 begin to sync binlog from GTID set 77263736-7899-11f0-81a5-0242ac120002:1-38
408408
[2025/08/25 15:29:09] [info] binlogsyncer.go:409 Connected to mysql 8.0.43 server
409-
INFO [Aug 25 15:29:09] connected to MySQL version 8.0.43
409+
INFO [2025-08-25T15:29:09-05:00] connected to MySQL version 8.0.43
410410
~~~
411411
412412
When rows are successfully replicated, you should see debug output like the following:
413413
414414
~~~
415-
DEBUG [Aug 25 15:29:38] upserted rows conflicts=0 duration=1.801ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
416-
DEBUG [Aug 25 15:29:38] progressed to consistent point: 77263736-7899-11f0-81a5-0242ac120002:1-39
415+
DEBUG [2025-08-25T15:29:38-05:00] upserted rows conflicts=0 duration=1.801ms proposed=1 target="\"molt\".\"public\".\"tbl1\"" upserted=1
416+
DEBUG [2025-08-25T15:29:38-05:00] progressed to consistent point: 77263736-7899-11f0-81a5-0242ac120002:1-39
417417
~~~
418418
</section>
419419
420420
<section class="filter-content" markdown="1" data-scope="oracle">
421421
When transactions are read from the Oracle source, you should see registered transaction IDs (XIDs):
422422
423423
~~~
424-
DEBUG [Jul 3 15:55:12] registered xid 0f001f0040060000
425-
DEBUG [Jul 3 15:55:12] registered xid 0b001f00bb090000
424+
DEBUG [2025-07-03T15:55:12-05:00] registered xid 0f001f0040060000
425+
DEBUG [2025-07-03T15:55:12-05:00] registered xid 0b001f00bb090000
426426
~~~
427427
428428
When rows are successfully replicated, you should see debug output like the following:
429429
430430
~~~
431-
DEBUG [Jul 3 15:55:12] upserted rows conflicts=0 duration=2.620009ms proposed=13 target="\"molt_movies\".\"USERS\".\"CUSTOMER_CONTACT\"" upserted=13
432-
DEBUG [Jul 3 15:55:12] upserted rows conflicts=0 duration=2.212807ms proposed=16 target="\"molt_movies\".\"USERS\".\"CUSTOMER_DEVICE\"" upserted=16
431+
DEBUG [2025-07-03T15:55:12-05:00] upserted rows conflicts=0 duration=2.620009ms proposed=13 target="\"molt_movies\".\"USERS\".\"CUSTOMER_CONTACT\"" upserted=13
432+
DEBUG [2025-07-03T15:55:12-05:00] upserted rows conflicts=0 duration=2.212807ms proposed=16 target="\"molt_movies\".\"USERS\".\"CUSTOMER_DEVICE\"" upserted=16
433433
~~~
434434
</section>
435435
@@ -732,8 +732,8 @@ On the target cluster, create a CockroachDB changefeed to send changes to MOLT R
732732
1. Verify that Replicator is reporting incoming HTTP requests from the changefeed. To do so, check the MOLT Replicator logs. Since you enabled debug logging with `-v`, you should see periodic HTTP request successes:
733733
734734
~~~
735-
DEBUG [Aug 25 11:52:47] httpRequest="&{0x14000b068c0 45 200 3 9.770958ms false false}"
736-
DEBUG [Aug 25 11:52:48] httpRequest="&{0x14000d1a000 45 200 3 13.438125ms false false}"
735+
DEBUG [2025-08-25T11:52:47-05:00] httpRequest="&{0x14000b068c0 45 200 3 9.770958ms false false}"
736+
DEBUG [2025-08-25T11:52:48-05:00] httpRequest="&{0x14000d1a000 45 200 3 13.438125ms false false}"
737737
~~~
738738
739739
These debug messages confirm successful changefeed connections to MOLT Replicator. You can disable verbose logging after verifying the connection.

src/current/molt/molt-fetch-commands-and-flags.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,7 @@ This page lists the [MOLT Fetch]({% link molt/molt-fetch.md %}) commands and the
5757
| <a id="metrics-listen-addr"></a> `--metrics-listen-addr` | Address of the Prometheus metrics endpoint, which has the path `{address}/metrics`. For details on important metrics to monitor, refer to [Monitoring]({% link molt/molt-fetch-monitoring.md %}).<br><br>**Default:** `'127.0.0.1:3030'` |
5858
| <a id="mode"></a> `--mode` | Configure the MOLT Fetch behavior: `data-load`, `export-only`, or `import-only`. For details, refer to [Fetch mode]({% link molt/molt-fetch.md %}#define-fetch-mode).<br><br>**Default:** `data-load` |
5959
| <a id="non-interactive"></a> `--non-interactive` | Run the fetch task without interactive prompts. This is recommended **only** when running `molt fetch` in an automated process (i.e., a job or continuous integration). |
60+
| <a id="opt-out-telemetry"></a> `--opt-out-telemetry` | Suppress MOLT telemetry-event logging, which is enabled by default. |
6061
| <a id="pglogical-replication-slot-name"></a> `--pglogical-replication-slot-name` | Name of a PostgreSQL replication slot that will be created before taking a snapshot of data. Must match the slot name specified with `--slotName` in the [MOLT Replicator command]({% link molt/molt-replicator.md %}#replication-checkpoints). For details, refer to [Initial bulk load (before replication)]({% link molt/molt-fetch.md %}#initial-bulk-load-before-replication). |
6162
| <a id="pglogical-publication-and-slot-drop-and-recreate"></a> `--pglogical-publication-and-slot-drop-and-recreate` | Drop the PostgreSQL publication and replication slot if they exist, then recreate them. Creates a publication named `molt_fetch` and the replication slot specified with `--pglogical-replication-slot-name`. For details, refer to [Initial bulk load (before replication)]({% link molt/molt-fetch.md %}#initial-bulk-load-before-replication).<br><br>**Default:** `false` |
6263
| <a id="pprof-listen-addr"></a> `--pprof-listen-addr` | Address of the pprof endpoint.<br><br>**Default:** `'127.0.0.1:3031'` |

src/current/molt/molt-fetch.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -767,13 +767,13 @@ A change data capture (CDC) cursor is written to the MOLT Fetch output as `cdc_c
767767
For MySQL:
768768

769769
~~~ json
770-
{"level":"info","type":"summary","fetch_id":"735a4fe0-c478-4de7-a342-cfa9738783dc","num_tables":1,"tables":["public.employees"],"cdc_cursor":"b7f9e0fa-2753-1e1f-5d9b-2402ac810003:3-21","net_duration_ms":4879.890041,"net_duration":"000h 00m 04s","time":"2024-03-18T12:37:02-04:00","message":"fetch complete"}
770+
{"level":"info","type":"summary","fetch_id":"735a4fe0-c478-4de7-a342-cfa9738783dc","num_tables":1,"tables":["public.employees"],"skipped_unmigratable_tables":[],"cdc_cursor":"b7f9e0fa-2753-1e1f-5d9b-2402ac810003:3-21","net_duration_ms":4879.890041,"net_duration":"000h 00m 04s","time":"2024-03-18T12:37:02-04:00","message":"fetch complete"}
771771
~~~
772772

773773
For Oracle:
774774

775775
~~~ json
776-
{"level":"info","type":"summary","fetch_id":"735a4fe0-c478-4de7-a342-cfa9738783dc","num_tables":3,"tables":["migration_schema.employees"],"cdc_cursor":"backfillFromSCN=26685444,scn=26685786","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:37:02-04:00","message":"fetch complete"}
776+
{"level":"info","type":"summary","fetch_id":"735a4fe0-c478-4de7-a342-cfa9738783dc","num_tables":3,"tables":["migration_schema.employees"],"skipped_unmigratable_tables":[],"cdc_cursor":"backfillFromSCN=26685444,scn=26685786","net_duration_ms":6752.847625,"net_duration":"000h 00m 06s","time":"2024-03-18T12:37:02-04:00","message":"fetch complete"}
777777
~~~
778778

779779
This `cdc_cursor` value is also included in the output of a fetch task from a PostgreSQL source. However, in the case of a PostgreSQL source, you can instead enable replication with the [`--pglogical-replication-slot-name`]({% link molt/molt-fetch-commands-and-flags.md %}#pglogical-replication-slot-name) and [`--pglogical-publication-and-slot-drop-and-recreate`]({% link molt/molt-fetch-commands-and-flags.md %}#pglogical-publication-and-slot-drop-and-recreate) flags, which must be defined.
@@ -1031,7 +1031,7 @@ molt fetch \
10311031
The output will include a `cdc_cursor` value at the end of the fetch task:
10321032

10331033
~~~ json
1034-
{"level":"info","type":"summary","fetch_id":"735a4fe0-c478-4de7-a342-cfa9738783dc","num_tables":1,"tables":["public.employees"],"cdc_cursor":"b7f9e0fa-2753-1e1f-5d9b-2402ac810003:3-21","net_duration_ms":4879.890041,"net_duration":"000h 00m 04s","time":"2024-03-18T12:37:02-04:00","message":"fetch complete"}
1034+
{"level":"info","type":"summary","fetch_id":"735a4fe0-c478-4de7-a342-cfa9738783dc","num_tables":1,"tables":["public.employees"],"skipped_unmigratable_tables":[],"cdc_cursor":"b7f9e0fa-2753-1e1f-5d9b-2402ac810003:3-21","net_duration_ms":4879.890041,"net_duration":"000h 00m 04s","time":"2024-03-18T12:37:02-04:00","message":"fetch complete"}
10351035
~~~
10361036

10371037
<section class="filter-content" markdown="1" data-scope="mysql oracle">

src/current/molt/replicator-metrics.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -439,17 +439,17 @@ replicator start \
439439
If successful, Replicator will start, and the console output will indicate that the snapshotter has started as well:
440440

441441
~~~
442-
INFO [Feb 2 10:20:32] Replicator starting
442+
INFO [2026-02-02T10:20:32-05:00] Replicator starting
443443
...
444-
INFO [Feb 2 10:20:32] metrics snapshotter started, writing to replicator-data/metrics-snapshots every 15s, retaining 168h0m0s
444+
INFO [2026-02-02T10:20:32-05:00] metrics snapshotter started, writing to replicator-data/metrics-snapshots every 15s, retaining 168h0m0s
445445
~~~
446446

447447
Upon interruption of Replicator, the snapshotter will be stopped:
448448

449-
~~~
450-
INFO [Feb 2 10:26:45] Interrupted
451-
INFO [Feb 2 10:26:45] metrics snapshotter stopped
452-
INFO [Feb 2 10:26:45] Server shutdown complete
449+
~~~
450+
INFO [2026-02-02T10:26:45-05:00] Interrupted
451+
INFO [2026-02-02T10:26:45-05:00] metrics snapshotter stopped
452+
INFO [2026-02-02T10:26:45-05:00] Server shutdown complete
453453
~~~
454454

455455
#### Step 2. Find the snapshot files in the data directory

0 commit comments

Comments
 (0)