jason810496 commented on code in PR #71704:
URL: https://github.com/apache/airflow/pull/71704#discussion_r3804225482
##########
airflow-core/docs/faq.rst:
##########
@@ -758,9 +765,47 @@ See :ref:`config:api__server_type`,
:ref:`config:api__worker_refresh_interval`,
.. note::
Worker recycling handles memory growth from *any* source, not just the Dag
cache.
- For production deployments, using both bounded caching and gunicorn worker
recycling
+ For production deployments, using both cache eviction and gunicorn worker
recycling
provides the best results.
+.. _faq:scheduler-memory-growth:
+
+How to prevent scheduler memory growth?
+----------------------------------------
+
+The scheduler caches serialized Dag objects for the life of the process, so as
Dag versions
+accumulate (see :ref:`faq:dag-version-inflation`) its memory grows until the
process is
+restarted or OOM killed. Configure eviction in the ``[scheduler]`` section:
Review Comment:
I intentionally to set the default size to no size limit but this doesn’t
means unbound. Since TTL will claim the stale dag version eventually. And user
can tune just the TTL or with the size limit.
--
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]
