Mysql source shows success but isn't successful

[razzeee]

Connector Name

source-mysql

Connector Version

3.50.8

What step the error happened?

During the sync

Relevant information

Sync finishes successful, but did not sync any data.

It also doesn't trigger the Successful syncs notification and also doesn't trigger the Failed syncs notification. I guess it's something else?

Relevant log output

>> ATTEMPT 1/1

2025-10-14 00:00:01 info APPLY Stage: BUILD — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info APPLY Stage: CLAIM — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info Claimed: true for workload 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover via API in dataplane AUTO9325096b-7d8c-4973-a567-fa84df9028b8 (b84f8ec1-a80f-4718-8c36-96cb150906bb)
2025-10-14 00:00:01 info APPLY Stage: LOAD_SHED — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info APPLY Stage: CHECK_STATUS — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info No pod found running for workload 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover
2025-10-14 00:00:01 info APPLY Stage: MUTEX — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info No mutex key specified for workload: 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover. Continuing...
2025-10-14 00:00:01 info APPLY Stage: ARCHITECTURE — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info APPLY Stage: LAUNCH — (workloadId=9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover)
2025-10-14 00:00:01 info [initContainer] image: airbyte/workload-init-container:1.8.5 resources: ResourceRequirements(claims=[], limits={}, requests={memory=0, cpu=0}, additionalProperties={})
2025-10-14 00:00:08 info Attempting to update workload: 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover to LAUNCHED.
2025-10-14 00:00:08 info Pipeline completed for workload: 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover.
2025-10-14 00:00:09 info 
2025-10-14 00:00:09 info ----- START DISCOVER -----
2025-10-14 00:00:09 info 
2025-10-14 00:00:11 info Connector exited, processing output
2025-10-14 00:00:11 info Output file jobOutput.json found
2025-10-14 00:00:11 info Connector exited with exit code 0
2025-10-14 00:00:11 info Reading messages from protocol version 0.2.0
2025-10-14 00:00:11 info INFO main i.m.c.e.DefaultEnvironment(<init>):168 Established active environments: [k8s, cloud, cli, source, connector]
2025-10-14 00:00:11 info INFO main i.a.i.s.m.MySqlSourceConfigurationFactory(makeWithoutExceptionHandling):138 SSL mode: preferred
2025-10-14 00:00:11 info INFO main i.a.i.s.m.MySqlSourceConfigurationFactory(makeWithoutExceptionHandling):162 maxConcurrencyLegacy: 1. maxDBConnections: null. socket paths: 0
2025-10-14 00:00:11 info INFO main i.a.i.s.m.MySqlSourceConfigurationFactory(makeWithoutExceptionHandling):181 Effective concurrency: 1
2025-10-14 00:00:11 info INFO main i.a.c.AirbyteConnectorRunnable(run):35 Executing class io.airbyte.cdk.discover.DiscoverOperation operation.
2025-10-14 00:00:11 info INFO main i.a.c.j.JdbcConnectionFactory(get):44 Creating new connection for 'jdbc:mysql://Toolsetsrv.dmz:3306'.
2025-10-14 00:00:11 info INFO main i.a.c.d.JdbcMetadataQuerier$memoizedTableNames$2(invoke):66 Querying table names for catalog discovery.
2025-10-14 00:00:11 info INFO main i.a.c.d.JdbcMetadataQuerier$memoizedTableNames$2(invoke):90 Discovered 164 table(s) in namespaces [toolset].
2025-10-14 00:00:11 info INFO main i.a.c.d.JdbcMetadataQuerier$memoizedColumnMetadata$2(invoke):104 Querying column names for catalog discovery.
2025-10-14 00:00:11 info INFO main i.a.c.d.JdbcMetadataQuerier$memoizedColumnMetadata$2(invoke):129 Discovered 1196 column(s) and pseudo-column(s).
2025-10-14 00:00:11 info INFO main i.a.i.s.m.MySqlSourceMetadataQuerier$memoizedPrimaryKeys$2(invoke):135 Querying MySQL system tables for all primary keys for catalog discovery.
2025-10-14 00:00:11 info INFO main i.a.i.s.m.MySqlSourceMetadataQuerier$memoizedPrimaryKeys$2(invoke):153 Discovered all primary keys in 1 MySQL schema(s).
2025-10-14 00:00:11 info INFO main i.a.c.d.JdbcMetadataQuerier(close):337 Closing JDBC connection.
2025-10-14 00:00:11 info INFO main i.a.c.AirbyteConnectorRunnable(run):47 Flushing output consumer prior to shutdown.
2025-10-14 00:00:11 info INFO main i.a.c.AirbyteConnectorRunnable(run):49 Completed integration: airbyte/source-mysql.
2025-10-14 00:00:11 info Checking for optional control message...
2025-10-14 00:00:11 info Writing catalog result to API...
2025-10-14 00:00:12 info Finished writing catalog result to API.
2025-10-14 00:00:12 info Writing output of 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover to the doc store
2025-10-14 00:00:12 info Marking workload 9c553bbd-409e-47af-8275-20c057903da7_1760313600000_discover as successful
2025-10-14 00:00:13 info 
2025-10-14 00:00:13 info Deliberately exiting process with code 0.
2025-10-14 00:00:13 info ----- END DISCOVER -----
2025-10-14 00:00:13 info 
2025-10-14 00:00:14 info APPLY Stage: BUILD — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info APPLY Stage: CLAIM — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info Claimed: true for workload 850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync via API in dataplane AUTO9325096b-7d8c-4973-a567-fa84df9028b8 (b84f8ec1-a80f-4718-8c36-96cb150906bb)
2025-10-14 00:00:14 info APPLY Stage: LOAD_SHED — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info APPLY Stage: CHECK_STATUS — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info No pod found running for workload 850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync
2025-10-14 00:00:14 info APPLY Stage: MUTEX — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info Mutex key: 850bbdfa-7a51-4b07-927a-e1d0a569511d specified for workload: 850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync. Attempting to delete existing pods...
2025-10-14 00:00:14 info Mutex key: 850bbdfa-7a51-4b07-927a-e1d0a569511d specified for workload: 850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync found no existing pods. Continuing...
2025-10-14 00:00:14 info APPLY Stage: ARCHITECTURE — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info APPLY Stage: LAUNCH — (workloadId=850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync)
2025-10-14 00:00:14 info [initContainer] image: airbyte/workload-init-container:1.8.5 resources: ResourceRequirements(claims=[], limits={memory=0, cpu=0}, requests={memory=0, cpu=0}, additionalProperties={})
2025-10-14 00:00:14 info Launching replication pod: replication-job-91-attempt-0 (selectors = {}) with containers:
2025-10-14 00:00:14 info [source] image: airbyte/source-mysql:3.50.8 resources: ResourceRequirements(claims=[], limits={memory=0, cpu=0}, requests={memory=0, cpu=0}, additionalProperties={})
2025-10-14 00:00:14 info [destination] image: airbyte/destination-postgres:2.4.7 resources: ResourceRequirements(claims=[], limits={memory=0, cpu=0}, requests={memory=0, cpu=0}, additionalProperties={})
2025-10-14 00:00:14 info [orchestrator] image: airbyte/container-orchestrator:1.8.5 resources: ResourceRequirements(claims=[], limits={memory=0, cpu=0}, requests={memory=0, cpu=0}, additionalProperties={})
2025-10-14 00:00:23 info Attempting to update workload: 850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync to LAUNCHED.
2025-10-14 00:00:23 info Pipeline completed for workload: 850bbdfa-7a51-4b07-927a-e1d0a569511d_91_0_sync.
2025-10-14 00:00:28 info Running replication worker...
2025-10-14 00:00:29 info Starting replication worker. job id: 91 attempt: 0
2025-10-14 00:00:29 info 
2025-10-14 00:00:29 info ----- START REPLICATION -----
2025-10-14 00:00:29 info 
2025-10-14 00:00:29 info Running destination...
2025-10-14 00:00:29 info Writing messages to protocol version 0.2.0
2025-10-14 00:00:29 info Reading messages from protocol version 0.2.0
2025-10-14 00:00:29 info Reading messages from protocol version 0.2.0
2025-10-14 00:00:29 info Starting workload heartbeat (interval=10s; timeout=600s)
2025-10-14 00:00:29 info SourceReader started.
2025-10-14 00:00:29 info DestinationWriter started.
2025-10-14 00:00:29 info DestinationReader started.
2025-10-14 00:00:29 info MessageProcessor started.
2025-10-14 00:00:29 info INFO main i.a.i.d.p.PostgresDestination$Companion(main):229 starting destination: class io.airbyte.integrations.destination.postgres.PostgresDestination
2025-10-14 00:00:29 info INFO main i.a.c.i.b.IntegrationCliParser$Companion(parseOptions):144 integration args: {catalog=/dest/catalog.json, write=null, config=/dest/connectorConfig.json}
2025-10-14 00:00:29 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):130 Running integration: io.airbyte.cdk.integrations.base.ssh.SshWrappedDestination
2025-10-14 00:00:29 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):131 Command: WRITE
2025-10-14 00:00:29 info INFO main i.a.c.i.b.IntegrationRunner(runInternal):132 Integration config: IntegrationConfig{command=WRITE, configPath='/dest/connectorConfig.json', catalogPath='/dest/catalog.json', statePath='null'}
2025-10-14 00:00:29 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword
2025-10-14 00:00:29 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword
2025-10-14 00:00:29 warn WARN main c.n.s.UnknownKeywordFactory(lambda$getKeyword$0):37 Unknown keyword multiline - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword or if it should generate annotations AnnotationKeyword
2025-10-14 00:00:29 info INFO main i.m.c.e.DefaultEnvironment(<init>):168 Established active environments: [k8s, cloud, cli, source, connector]
2025-10-14 00:00:29 info INFO main i.a.c.i.b.s.SshWrappedDestination(getSerializedMessageConsumer):112 No SSH connection options found, using defaults
2025-10-14 00:00:29 info INFO main i.a.c.i.b.s.SshTunnel$Companion(getInstance):424 Starting connection with method: NO_TUNNEL
2025-10-14 00:00:29 info INFO main c.z.h.HikariDataSource(<init>):79 HikariPool-1 - Starting...
2025-10-14 00:00:29 info INFO main c.z.h.HikariDataSource(<init>):81 HikariPool-1 - Start completed.

[...]

2025-10-14 00:48:36 info Records read: 2475000 (474 MB)
2025-10-14 01:22:20 error Failed to obtain or add access token
2025-10-14 01:37:06 error Failed to obtain or add access token
2025-10-14 02:25:04 error DestinationWriter error: 
2025-10-14 02:25:04 error DestinationWriter error: 
2025-10-14 02:25:04 warn Attempted to close a destination which is already closed.
2025-10-14 02:25:04 info DestinationWriter finished.
2025-10-14 02:25:04 error No successful heartbeat in the last 600s; exiting.
2025-10-14 02:25:04 error DestinationReader error: 
2025-10-14 02:25:04 info MessageProcessor finished.
2025-10-14 02:25:04 info DestinationReader finished.
2025-10-14 02:25:04 info INFO DefaultDispatcher-worker-3 i.a.c.r.JdbcSelectQuerier$Result(close):173 Closing SELECT `id`, `lat`, `lng`, `cost`, `hours`, `notes`, `payed`, `billed`, `created`, `task_id`, `user_id`, `log_date`, `modified`, `stop_time`, `adjustment`, `project_id`, `start_time`, `task_group_id`, `approve_status`, `is_timer_record`, `document_status_id`, `project_schedule_id` FROM `toolset`.`zst_time_sheet_tbl` WHERE `id` <= ?
2025-10-14 02:25:04 info INFO DefaultDispatcher-worker-3 i.a.c.r.FeedReader(readPartitionWithResources):251 releasing resources acquired to read partition 1 for 'toolset.zst_time_sheet_tbl' in round 1
2025-10-14 02:25:04 error SourceReader error: 
2025-10-14 02:25:04 info SourceReader finished.
2025-10-14 02:25:04 error runJobs failed; recording failure but continuing to finish.
2025-10-14 02:25:04 info Closing StateCheckSumCountEventHandler
2025-10-14 02:25:06 info 
----- START POST REPLICATION OPERATIONS -----


2025-10-14 02:25:06 info No post-replication operation(s) to perform.
2025-10-14 02:25:06 info 
----- END POST REPLICATION OPERATIONS -----

Contribute

• Yes, I want to contribute

[camille-lemaitre]

Having the same issue with Postgre.
I realised in the replication pod logs that the error is actually an OutofMemory issue.

[stevanthomas-nf53]

Having the same issue in mssql-server with a snowflake destination.

@camille-lemaitre I will retry with a larger warehouse and see if that does the trick.

[stevanthomas-nf53]

@razzeee I've been fiddling around the logs and I see that errors are not reported correctly and hence the sync shows up as successful, when it reality it has failed because of an error.

In your case, looking at the logs I see this:
2025-10-14 01:22:20 error Failed to obtain or add access token

I discovered an error hidden in my logs as well.

[andrespp]

Same issue here. The replication pod was stuck Pending with “Insufficient cpu” in pod events (VM had 4 vCPUs). Increasing the VM to 6 vCPUs fixed it.

[snorrehu]

Seeing the exact same thing with connector Google Cloud Storage connector version 0.8.30. Will attempt to update to 0.9.1