Source process exited with non-zero exit code 137

The error message "Source process exited with non-zero exit code 137" typically indicates that the source connector process was terminated by the operating system, often due to running out of memory (OOM). This can happen for various reasons, such as processing large files or handling large datasets. Here are some specific instances and potential causes based on the knowledge sources: 1. source-salesforce Connector: - Connector Version: 2.5.2 - Issue: The error occurs when pulling a particular schema out of Salesforce, but not for other schemas. - Logs:

2024-04-17 02:30:33 platform > Workload 16ec58e2-4d17-409a-aa1c-5e8e72d24a5e_10587463_2_sync is running      2024-04-17 02:31:03 platform > Workload 16ec58e2-4d17-409a-aa1c-5e8e72d24a5e_10587463_2_sync has returned a terminal status of failure. Fetching output...

- Link: [source-salesforce issue](https://github.com/airbytehq/airbyte/issues/37368) 2. source-file Connector: - Connector Version: 0.3.12 - Issue: A user speculated that a large parquet file (115 MB) might be causing the issue. - Logs:

[b66d0cb9_6612_456c_8baf_41115c3a838f_logs_7_txt.txt](<https://github.com/airbytehq/airbyte/files/12833570/b66d0cb9_6612_456c_8baf_41115c3a838f_logs_7_txt.txt>)

- Link: [source-file issue](https://github.com/airbytehq/airbyte/issues/31131) 3. source-file Connector: - Connector Version: 0.3.11 - Issue: Encountered when using the file source connector to a StarRocks destination connector. - Logs:

shell      I'll upload the file.

- Link: [source-file issue](https://github.com/airbytehq/airbyte/issues/27696) ### Actionable Steps 1. Increase Memory Allocation: - Ensure that the system running the Airbyte connectors has sufficient memory. You may need to increase the memory limits for the Docker containers or Kubernetes pods running the connectors. 2. Optimize Data Processing: - For large files or datasets, consider breaking them into smaller chunks to reduce memory usage during processing. 3. Monitor System Resources: - Use monitoring tools to keep an eye on memory usage and other system resources to identify potential bottlenecks. 4. Review Connector Configuration: - Check the configuration settings for the connectors to ensure they are optimized for your specific use case. If the issue persists, you may want to provide more detailed logs and context to the Airbyte community or support team for further assistance. For more information, you can refer to the specific issues linked above: - [source-salesforce issue](https://github.com/airbytehq/airbyte/issues/37368) - [source-file issue](https://github.com/airbytehq/airbyte/issues/31131) - [source-file issue](https://github.com/airbytehq/airbyte/issues/