csm10495 commented on issue #21078: URL: https://github.com/apache/airflow/issues/21078#issuecomment-1241407443
Part of the problem here is the original problem is pretty difficult to reproduce... we didn't hit it continually, just was a weird once in a while thing. Changing these settings to the super high values are just to reproduce the issue more consistently. I'm not really worried about the failure as much as no logs coming up in the web ui for certain task failures. From the code logic, if the db is in limbo, I can see how it would be tough to still ensure logs come out. Maybe a middle ground would be to have the UI tell the user to ask their administrator to check the scheduler logs around the task start time in the event of a completed task with no logs at all... since any info is likely there. That would be much better than just a blank page. In terms of Postgres, I'll ask but I don't think its really swap-able in our current production environment. I'll just close this out. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
