Hi all, we have airbyte open source deployed on ec2. After the instance got stuck and we restarted it, airbyte tries to sync all pipelines at the same time and causes the ec2 instance to get stuck again. Any suggestions to prevent this? Are there some settings I should use in the .env file

Based on the information provided in the extracts, it seems like you might be encountering issues due to the concurrent execution of multiple sync jobs. One way to manage this could be to take advantage of job concurrency settings. In a previous support conversation on Slack, a user asked about running multiple streams from the same source and whether they should run all the streams in one job or split them to take advantage of job concurrency. The support team suggested splitting the streams and referred to a document on scaling Airbyte. You can find this document [here](https://docs.airbyte.com/operator-guides/scaling-airbyte/). However, the extracts do not provide specific details on how to configure these settings in the .env file. It's recommended to refer to the official Airbyte documentation or reach out to the Airbyte community for more specific guidance.