uranusjr commented on code in PR #71814:
URL: https://github.com/apache/airflow/pull/71814#discussion_r3811509508
##########
airflow-core/docs/administration-and-deployment/web-stack.rst:
##########
@@ -188,9 +188,10 @@ For example, to trigger a rolling restart of the API
server pods:
kubectl rollout restart deployment airflow-api-server
-The API server also supports bounded DAG caching via ``dag_cache_size`` and
-``dag_cache_ttl``, which limits memory consumed by cached SerializedDAG
objects.
-This reduces memory growth from DAG version accumulation regardless of server
type.
+The API server also evicts cached SerializedDAG objects via ``dag_cache_size``
and
+``dag_cache_ttl``, which reduces memory growth from Dag version accumulation
regardless of
+server type. Note that only ``dag_cache_size`` caps memory outright: each
re-check resets a
+cached entry's expiry, so ``dag_cache_ttl`` reclaims only the versions that
stop being requested.
Review Comment:
This is _slightly_ overstating. The TTL is refreshed only at revalidation
boundaries, not on every request. If an operator sets `dag_cache_ttl <
min_serialized_dag_update_interval`, an actively-requested entry can still
expire and reload between revalidations.
--
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]
