Hello, we have a t2.medium AWS instance where I ru...
# replication-ask-ai
a
Hello, we have a t2.medium AWS instance where I run the latest Airbyte version. I have 7 different Mongodb -> BigQuery connections running every 6 hours, but with 10-20-minute gaps between them. They each take up to 12 minutes. About 20 hours ago I stopped the instance and started again today, which caused the jobs to start for all 7 connections. That made airbyte and the instance unresponsive and they still haven't recovered even after a reboot. Is this normal?
k
New message text here
a
We have staggered the syncs though. What caused the issue was all of them starting together because of a period of inactivity of the instance. Shouldn't the cron schedules have continued as normal instead of all of them starting together, since there is a limit to how many can run simultaneously?