Issue with abctl migration causing app crash and 500 errors

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

After migrating from compose to abctl, running syncs crashes the app with 500 errors and stops the EC2 instance. Possible minimal requirements or misconfiguration.


Question

Hello everyone! I have a problem. After migrate the compose to abctl. Doing the abctl local install --migrate works. But when running syncs it crashes the whole app and starts throwing 500 error. 503 and then just stops working the ec2 instance. are there minimal requeriments for the instance or something i havent configured properly???


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

["abctl-migration", "app-crash", "500-error", "ec2-instance", "minimal-requirements", "misconfiguration"]
2

With all Airbyte components and connectors running on single EC2 instance I’d start with 16GB, 8vCPU. Requirements depend heavily how many synchronizations will be running simultaneously. What kind of connectors Java-based or Python-based will be used, etc.

In this thread you can find some handy instructions for troubleshooting https://airbytehq.slack.com/archives/C021JANJ6TY/p1723112410442379?thread_ts=1723112119.608099&cid=C021JANJ6TY