Issue Description
When allow_no_etl is set to true and etl_sources are misconfigured (inaccessible IP or port), Clio seems to be using 100% of all cores available. Presumably it's an edge case in the new ETL.
Expected Result
No significant CPU usage as nothing should be going on.
Actual Result
100% of all cores are red.
Issue Description
When
allow_no_etlis set totrueandetl_sourcesare misconfigured (inaccessible IP or port), Clio seems to be using 100% of all cores available. Presumably it's an edge case in the new ETL.Expected Result
No significant CPU usage as nothing should be going on.
Actual Result
100% of all cores are red.