bhavaniravi commented on issue #9643: URL: https://github.com/apache/airflow/issues/9643#issuecomment-723395297
This issue has popped up again. Clearly, it is an infra issue, but my question is would it be better to handle `OperationalError` in airflow. We had the same issue in the task code. We were able to close the connection in case of an error and retry something like this. ``` BEGIN if that fails -> close connection -> open new -> try to start transaction again ``` The problem is we cannot do the same for airflow, thereby leading to failures when 1. Updating the task status 2. Logging @potiuk @mik-laj ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
