Sync job failuring and retries itself after successfuly done

Connector Questions & Issues
,
1
  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu
  • Memory / Disk:
  • Deployment: Kubernetes
  • Airbyte Version: 0.36.0-alpha
  • Source name/version: Google Analytics (0.1.18)
  • Destination name/version: Redshift (0.3.28)
  • Step: The issue is happening during sync
  • Description:

The connector from Google Analytics to Redshift is reporting the erros: “ERROR i.a.w.DefaultReplicationWorker(run):169 - Sync worker failed.” and ERROR i.a.i.d.b.BufferedStreamConsumer(close):191 - Close failed. despite these erros the logs reports that the Sync was completed successfully. Below the logs.
logs-112.txt (30.0 KB)

2

how much resources memory/disk the cluster have?

4

@marcosmarxm

webapp:
Memory: 1Gi / CPU: 1

scheduler:
Memory: 1Gi / CPU: 1

podSweeper:
Memory: 512Mi / CPU: 500m

Server:
Memory: 6Gi / CPU: 2

Worker:
Memory: 1Gi / CPU: 1

5

Can you increase the worker memory?

6

Also could you try a toy connector like PokeAPI to your destination just to validate the pipeline is working?

7

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.