Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Source S3: Cannot allocate memory #6606

Closed
harshithmullapudi opened this issue Oct 1, 2021 · 0 comments · Fixed by #6615
Closed

Source S3: Cannot allocate memory #6606

harshithmullapudi opened this issue Oct 1, 2021 · 0 comments · Fixed by #6615

Comments

@harshithmullapudi
Copy link
Contributor

Enviroment

OS Version / Instance: EC2 t2.medium
Memory / Disk: 4Gb / 16Gb
Deployment: Docker
Airbyte Version: 0.29.22-alpha
Source name/version: S3 0.1.3
Destination name/version: Postgres 0.3.7
Step: Synching

Current Behavior

One of my connections suddenly runs out of memory while inferring the schema. It works well for a couple of days/weeks and then can't sync anymore. It happened already ~two weeks ago, I "solved" the issue by upgrading to a newest version.
Upon further inspection, I can see that earlier this week, some of the attempts failed, but the 2nd or 3rd one succeeded. Interestingly too, successful attempts usually still timed out at some point while inferring the schema. Size of the files doesn't seem to have an impact (the biggest file was 147.4KB and was sync last month, usually they are around 50KB). The only difference with my other S3 connections is that this specific streams deals with multiple files per sync.
I tried to reduced the block size as well, but to no avail. I also tried to provide the schema as an input but same same.
Attached you'll find logs of a successful run as well as one that failed.

Expected Behavior

Tell us what should happen.

Logs

If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.

LOG

replace this with
your long log
output here

Steps to Reproduce

Are you willing to submit a PR?

Remove this with your answe
logs-2724-2.txt
logs-2570-2.txt
r.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants