Confluence -> Postgres sync always erroring out

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: MacOS
  • Memory / Disk: 16GB / 500 GB
  • Deployment: Docker but running locally on localhost:8000
  • Airbyte Version: 610c9c01df8b9b431a27837aa8761a712332ff22 commit on Github
  • Source name/version: Confluence 0.1.1
  • Destination name/version: Postgres 1.0.45
  • Step: Sync
  • Description: I am able to create my Confluence source and Postgres destination. Testing and setting up the connection works for both. However, when I try to sync, I get an exception saying Thread starvation or clock leap detected. Specifically
2023-02-22 05:37:28 source > Starting syncing SourceConfluence
2023-02-22 05:37:28 source > Syncing stream: pages 
2023-02-22 05:38:24 WARN c.n.s.JsonMetaSchema(newValidator):278 - Unknown keyword user - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2023-02-22 05:38:47 destination > integration args: {catalog=destination_catalog.json, write=null, config=destination_config.json}
2023-02-22 05:38:48 destination > Running integration: io.airbyte.integrations.base.ssh.SshWrappedDestination
2023-02-22 05:38:49 destination > Command: WRITE
2023-02-22 05:39:04 destination > Integration config: IntegrationConfig{command=WRITE, configPath='destination_config.json', catalogPath='destination_catalog.json', statePath='null'}
2023-02-22 05:41:54 destination > Unknown keyword order - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2023-02-22 05:41:56 destination > Unknown keyword airbyte_secret - you should define your own Meta Schema. If the keyword is irrelevant for validation, just use a NonValidationKeyword
2023-02-22 05:51:44 destination > Starting connection with method: NO_TUNNEL
2023-02-22 05:54:02 destination > HikariPool-1 - Starting...
2023-02-22 05:54:03 destination > HikariPool-1 - Start completed.
2023-02-22 05:54:04 destination > Write config: WriteConfig{streamName=pages, namespace=null, outputSchemaName=public, tmpTableName=_airbyte_tmp_jyl_pages, outputTableName=_airbyte_raw_pages, syncMode=overwrite}
2023-02-22 05:54:05 destination > class io.airbyte.integrations.destination.buffered_stream_consumer.BufferedStreamConsumer started.
2023-02-22 05:54:05 destination > Preparing tmp tables in destination started for 1 streams
2023-02-22 05:54:05 destination > Preparing tmp table in destination started for stream pages. schema: public, tmp table name: _airbyte_tmp_jyl_pages
2023-02-22 05:54:08 destination > Preparing tables in destination completed.
2023-02-22 06:07:10 destination > HikariPool-1 - Thread starvation or clock leap detected (housekeeper delta=1m18s254ms252µs371ns).

with the full log attached below. I’m pretty sure the Postgres destination is set-up correctly since I was able to sync Pokeapi through to it without many issues, but it says the error is in the destination. Another note: Whenever I try this connector, the first two attempts always fail too and the starvation ends up on the third attempt.

Any advice for how to proceed? Thanks!

522fb751_ba48_4462_b1a1_824037ff5dc9_logs_5_txt (1).txt (94.6 KB)

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team