[GitHub] [airflow] potiuk edited a comment on pull request #19860: Restore stability and unquarantine all test_scheduler_job tests

[GitBox <gi...@apache.org>]

potiuk edited a comment on pull request #19860:
URL: https://github.com/apache/airflow/pull/19860#issuecomment-983543457


   > Would changing our logging config/setup so we don't need to re-load settings help here do you think, or is this just a symptom of the problem but not the cause?
   
   If we do not to do any "ORM reload magic" at the start of the DagProcessor, I believe it would help. The "spawned" processes are supposed to work just fine, but I think in this case we are likely hitting some optimisations and shared memory reused by the c- libraries in the database drivers, that are likely corrupted during the reinitialisation of the ORM. It's like the same library is initialized twice I think, where it should not - and that's the root cause of the problem IMHO.
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org