Summary
Error encountered when syncing data from a parquet file to MongoDB with non-zero exit code 3. Complete log file provided for reference.
Question
Hi Everyone,
I’d like to ask. When I sync data from the parquet file to MongoDB, I get the error “Destination process exited with non-zero exit code 3.” Here is the complete log file. Any help would be greatly appreciated!
thank you
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["sync-data", "parquet-file", "mongodb", "error", "non-zero-exit-code"]
could you maybe share also just the destination logs…? That might be helpful 
where can I get the destination log?
there are 5 toggles at the top (under the yellow warning and search logs bar). If you deselect everything except destination, I think you might get a more informative error message.
line 249
> 2024-07-15 03:08:02 destination > Terminating due to java.lang.OutOfMemoryError: Java heap space
if you don’t normally have this error, I think it could be related to the resources available at the time
otherwise, this might be helpful:
https://docs.airbyte.com/operator-guides/scaling-airbyte#memory
good luck!
If the parameters have been changed in the .env section, will the config be applied immediately? Or do I have to restart Docker?
I’ve never used Airbyte with Docker, but I did have to delete the pods for the Kubernetes deployment for the changes to go through.