potiuk opened a new pull request #18054:
URL: https://github.com/apache/airflow/pull/18054


   Extends the standard python logging.FileHandler with advise to the
   Kernel to not cache the file in PageCache when it is written. While
   there is nothing wrong with such cache (it will be cleaned when memory
   is needed), it causes ever-growing memory usage when scheduler is
   running as it keeps on writing new log files and the files are not
   rotated later on. This might lead to confusion for our users, who are
   monitoring memory usage of Scheduler - without realising that it is
   harmless and expected in this case.
   
   Adding the advice to Kernel might help with not generating the cache
   memory growth in the first place.
   
   Closes: #14924
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   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 change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


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