Restart an existing failed sync from tmp tables

Connector Questions & Issues
,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 4Gb / 50 GB
  • Deployment: Docker
  • Airbyte Version: What version are you using now?
  • Source name/version: S3
  • Destination name/version: Postgres
  • Step: Sync
  • Description: I had run a sync of around 30gb of data, the data download and creation of tmp tables was complete and the job was stuck at Executing finalization of tables. Because of the volume of data or the streas this was stuck at this for more than 5 6 hours. I had to cancel the job as the sync time was too long.
    I can see that the data has been downloaded to the server and is available i the tmp tables, is it possible to move the data after normalization to the main table. I tried running sync again it restarted by downloading the data again.
2

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.
Best,
The Community Assistance Team

3

Hey thanks for reaching out to us. Could you help with sync logs here maybe share the file here for further diagnosis of the issue?

4

Hello! I have a similar problem.
Source: S3
Destination: yandex clickhouse

There are several *.csv.gz files in the source, with a total volume of about 18GB. The replication process hangs at the “Executing finalization of tables.”
log in attachment

d37b7581_ec1c_48af_90be_08af776c1293_logs_493_txt.txt (1.1 MB)

5

Hey thanks for reaching out. Could you check the resources and see if that available enough so to make the replication process smooth?

6

Airbyte server:
vCPUs: 8
RAM: 16GB
HDD: 50Gb

Clickhouse server:
vCPUs: 4
RAM: 16GB
SSD: 150Gb

Monitoring in the course of replication of critical showed nothing.
Last query captured in clickhouse

INSERT INTO target_table
SELECT * FROM _airbyte_tmp_juh_target_table

After that, as if nothing happened, but the process never ended.

7

Maybe this can be of some help. Launched Airbyte with LOG_LEVEL=TRACE.
Now in the logs:

2022-11-10 11:50:12 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:50:22 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:50:32 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:50:42 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:50:52 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:51:02 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:51:12 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:51:22 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:51:32 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:51:42 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:51:52 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:52:02 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:52:12 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:52:22 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:52:32 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
2022-11-10 11:52:42 DEBUG i.a.c.h.LogClientSingleton(setJobMdc):135 - Setting docker job mdc
8

Hello programmeddeath1, it’s been a while without an update from us. Are you still having problems or did you find a solution?