wookiist opened a new pull request, #30623:
URL: https://github.com/apache/airflow/pull/30623

   # Description
   This PR attaches the logGroomer sidecar pod when using a standalone `dag 
processor`. This is to prevent scheduler logs from growing infinitely in the 
`logs` directory of that `dag processor` pod. 
   
   In fact, one of the Airflow clusters my team uses had about `3.5 TiB` of 
scheduler logs accumulated in the emptyDir of a `dag processor` pod, which 
reduced the ephemeral-storage availability on that node to the point of pod 
eviction, resulting in a pod eviction.
   
   ```
   airflow@airflow-test-dag-processor-78f9bfdb88-hmckb:/opt/airflow/logs$ ls
   scheduler
   airflow@airflow-test-dag-processor-78f9bfdb88-hmckb:/opt/airflow/logs$ du -sh
   3.5T      .
   ```
   
   We haven't figured out why the standalone `dag processor` was accumulating 
scheduler logs, but we think it's a good idea to attach a logGroomer sidecar 
like any other scheduler pod or worker pod to prevent this from happening in 
the first place. 
   
   In this PR, we've modified the helm chart to attach a logGroomer to the 
standalone `dag processor`.
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


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