potiuk commented on issue #19192: URL: https://github.com/apache/airflow/issues/19192#issuecomment-1143415256
> @bh-ashishsharma :We "fixed it" by allocating more memory to our running containers on Kubernetes. Since then we have not seen the issue. Well. Increasing resource usage when you do not have enough of them is really good fix. Unfortunately only your deploymenent can monitor and indicate if you lack memory or not, so this was indeed a fix to a deployment issue. Good to know - we would likely have a good case to explain to others to pay attention to. @khintz - maybe you would like to make a PR to our docs describing what you observed and remediation that you applied ? I think the best approach is to modify this doc: https://airflow.apache.org/docs/apache-airflow/stable/production-deployment.html#scheduler-uptime It's super easy - just use "Suggest change on this page" link at top-bottom and it will open a GitHub UI where you will be able to make changes to the docs directly using GitHub UI - without any need for any environment. -- 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]
