Will-thom commented on PR #67393:
URL: https://github.com/apache/airflow/pull/67393#issuecomment-4609105073

   The motivation is to make the Redis maintenance boundary explicit for 
CeleryExecutor users.
   
   The linked issue asks what Airflow stores in Redis and whether it is safe to 
clean it. Today the docs explain Redis as the broker, but they do not clearly 
distinguish broker-side transient Celery state from the Airflow metadata 
database, nor warn that flushing Redis while schedulers/workers are active can 
drop queued work or make task state inconsistent.
   
   This section is meant to prevent operators from treating Redis cleanup like 
`airflow db clean`: metadata cleanup and broker cleanup affect different stores 
and need different safety conditions.


-- 
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]

Reply via email to