https://linen.dev logo
Join Slack
Powered by
```2026-05-26 01:55:02 platform INFO APPLY Stage: ...
# replication-ask-ai
r
Copy code
2026-05-26 01:55:02 platform INFO APPLY Stage: BUILD — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO APPLY Stage: CLAIM — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO Claimed: true for workload d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover via API in dataplane 5c1bb50d-f275-4f4f-932d-5ee746c97298 (161a707b-61cb-403b-9bba-eb93de9afa0e)
2026-05-26 01:55:02 platform INFO APPLY Stage: LOAD_SHED — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO APPLY Stage: CHECK_STATUS — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO No pod found running for workload d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover
2026-05-26 01:55:02 platform INFO APPLY Stage: MUTEX — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO No mutex key specified for workload: d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover. Continuing...
2026-05-26 01:55:02 platform INFO APPLY Stage: ARCHITECTURE — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO APPLY Stage: LAUNCH — (workloadId=d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover)
2026-05-26 01:55:02 platform INFO [initContainer] image: airbyte/workload-init-container:2.1.0 resources: ResourceRequirements(claims=[], limits={}, requests={}, additionalProperties={})
2026-05-26 01:55:10 platform INFO Attempting to update workload: d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover to LAUNCHED.
2026-05-26 01:55:10 platform INFO Pipeline completed for workload: d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover.
2026-05-26 01:55:13 platform INFO
2026-05-26 01:55:13 platform INFO Transitioning workload to running state
2026-05-26 01:55:13 platform INFO Connector exited, processing output
2026-05-26 01:55:13 platform INFO ----- START DISCOVER -----
2026-05-26 01:55:13 platform INFO Output file jobOutput.json found
2026-05-26 01:55:13 platform INFO
2026-05-26 01:55:13 platform INFO Connector exited with exit code 0
2026-05-26 01:55:13 source INFO Reading messages from protocol version 0.2.0
2026-05-26 01:55:13 source INFO i.a.i.s.m.MySqlSource(main):534 starting source: class io.airbyte.integrations.source.mysql.MySqlSource
2026-05-26 01:55:13 source INFO i.a.i.b.IntegrationCliParser(parseOptions):126 integration args: {discover=null, config=/config/connectionConfiguration.json}
2026-05-26 01:55:13 source INFO i.a.i.b.IntegrationRunner(runInternal):132 Running integration: io.airbyte.integrations.base.ssh.SshWrappedSource
2026-05-26 01:55:13 source INFO i.a.i.b.IntegrationRunner(runInternal):133 Command: DISCOVER
2026-05-26 01:55:13 source INFO i.a.i.b.IntegrationRunner(runInternal):134 Integration config: IntegrationConfig{command=DISCOVER, configPath='/config/connectionConfiguration.json', catalogPath='null', statePath='null'}
2026-05-26 01:55:13 source WARN c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2026-05-26 01:55:13 source WARN c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2026-05-26 01:55:13 source WARN c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword always_show - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2026-05-26 01:55:13 source WARN c.n.s.JsonMetaSchema(newValidator):278 Unknown keyword display_type - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2026-05-26 01:55:13 source INFO i.a.i.b.s.SshTunnel(getInstance):204 Starting connection with method: NO_TUNNEL
2026-05-26 01:55:13 source INFO c.z.h.HikariDataSource(<init>):80 HikariPool-1 - Starting...
2026-05-26 01:55:13 source INFO c.z.h.HikariDataSource(<init>):82 HikariPool-1 - Start completed.
2026-05-26 01:55:13 source INFO i.a.i.s.j.AbstractJdbcSource(discoverInternal):170 Internal schemas to exclude: [information_schema, performance_schema, mysql, sys]
2026-05-26 01:55:13 source INFO i.a.i.s.j.AbstractJdbcSource(discoverPrimaryKeys):277 Discover primary keys for tables: [BYBIT_FILE_INFO, AWS_FILE_INFO, AWSQA_FILE_INFO, ERROR_INFO, PHASE_INFO, MS_FILE_INFO, TER_FILE_INFO, NOTES, STRING_ID, LRCS_PHASE_GRADING, BYBIT_EXT_PHASE_INFO, MS_IN_PHASE_INFO, MS_EXT_PHASE_INFO, AWS_EXT_PHASE_INFO, EXPANSION_DATA, TER_EXT_PHASE_INFO, AWSQA2_FILE_INFO, PED_DATA, AWS_IN_PHASE_INFO, AWSQA2_REVIEW_INFO, TER_IN_PHASE_INFO, FILE_INFO, BYBIT_IN_PHASE_INFO, LRCS_PHASE_INFO, AWSQA_REVIEW_INFO]
2026-05-26 01:55:13 source INFO c.z.h.HikariDataSource(close):350 HikariPool-1 - Shutdown initiated...
2026-05-26 01:55:13 source INFO c.z.h.HikariDataSource(close):352 HikariPool-1 - Shutdown completed.
2026-05-26 01:55:13 source INFO i.a.i.b.IntegrationRunner(runInternal):228 Completed integration: io.airbyte.integrations.base.ssh.SshWrappedSource
2026-05-26 01:55:13 source INFO i.a.i.s.m.MySqlSource(main):536 completed source: class io.airbyte.integrations.source.mysql.MySqlSource
2026-05-26 01:55:13 platform INFO Checking for optional control message...
2026-05-26 01:55:13 platform INFO Writing catalog result to API...
2026-05-26 01:55:13 platform INFO Workload successfully transitioned to running state
2026-05-26 01:55:13 platform INFO Finished writing catalog result to API.
2026-05-26 01:55:13 platform INFO Writing output of d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover to the doc store
2026-05-26 01:55:13 platform INFO Marking workload d6909882-e0ea-48d3-9085-1af8bc09d621_1779753600000_discover as successful
2026-05-26 01:55:13 platform INFO
2026-05-26 01:55:13 platform INFO Deliberately exiting process with code 0.
2026-05-26 01:55:13 platform INFO ----- END DISCOVER -----
2026-05-26 01:55:13 platform INFO
2026-05-26 01:55:15 platform INFO APPLY Stage: BUILD — (workloadId=07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync)
2026-05-26 01:55:15 platform INFO APPLY Stage: CLAIM — (workloadId=07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync)
2026-05-26 01:55:15 platform INFO Claimed: true for workload 07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync via API in dataplane 5c1bb50d-f275-4f4f-932d-5ee746c97298 (161a707b-61cb-403b-9bba-eb93de9afa0e)
2026-05-26 01:55:15 platform INFO APPLY Stage: LOAD_SHED — (workloadId=07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync)
2026-05-26 01:55:15 platform INFO APPLY Stage: CHECK_STATUS — (workloadId=07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync)
2026-05-26 01:55:15 platform INFO No pod found running for workload 07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync
2026-05-26 01:55:15 platform INFO APPLY Stage: MUTEX — (workloadId=07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync)
2026-05-26 01:55:15 platform INFO Mutex key: 07691b4d-6587-4097-a326-ceac8512b9c2 specified for workload: 07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync. Attempting to delete existing pods...
2026-05-26 01:55:15 platform INFO Existing pods for mutex key: 07691b4d-6587-4097-a326-ceac8512b9c2 deleted.
2026-05-26 01:55:15 platform INFO APPLY Stage: ARCHITECTURE — (workloadId=07691b4d-6587-4097-a326-ceac8512b9c2_18768_0_sync)
k
The logs you've shared show a MySQL source DISCOVER workload followed by the beginning of a SYNC workload. Here's a breakdown of what's happening: DISCOVER Workload (completed successfully) The discover job ran cleanly: 1. BUILD → CLAIM → LOAD_SHED → CHECK_STATUS → MUTEX → ARCHITECTURE → LAUNCH — the workload pipeline stages all applied normally. 2. No existing pod was found (expected for a fresh workload), and no mutex key was needed for a discover job. 3. The init container (
airbyte/workload-init-container:2.1.0
) launched with no resource limits/requests set. 4. The connector (
MySqlSource
) ran a DISCOVER command using 
NO_TUNNEL
(no SSH tunnel), connected via HikariCP, discovered primary keys for 25 tables, and completed successfully with exit code 0. 5. The catalog was written to the API and the workload was marked successful. SYNC Workload (starting) The sync job (
07691b4d-..._18768_0_sync
) then began: • It was claimed by the same dataplane. • A mutex key (
07691b4d-6587-4097-a326-ceac8512b9c2
) was specified — this is expected for sync jobs to prevent concurrent runs of the same connection. Existing pods for that mutex key were deleted before proceeding. • The log cuts off at the ARCHITECTURE stage, so the sync launch outcome isn't shown. Notable Observations • The 
WARN
messages about unknown JSON schema keywords (
order
, 
airbyte_secret
, 
always_show
, 
display_type
) are harmless — they are standard warnings from the JSON schema validator and do not indicate errors. • The discover completed very quickly (~11 seconds total), which is normal for a small schema (25 tables). • No errors are present in the provided logs. If you're experiencing an issue with the sync job that follows, please share the rest of the sync logs for further diagnosis. [workload DB schema] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.
20 Views
Open in Slack
PreviousNext
Powered by