zsdyx commented on issue #28740: URL: https://github.com/apache/airflow/issues/28740#issuecomment-2522721849
> > Hi @rinzool, Do you know why this is, is it because of the behavior of the linux kernel, the first time you encounter this problem, why is it GC after setting limit. > > Honestly no. My supposition is that the scheduler has an internal process to release some memory when it reaches a limit (like 90% of available memory for example), and by defining a memory limit to the pod it helps airflow to trigger this process. But honestly I don't know if that's the real reason. All I know is that it fixed my problem 🤷 We use the same version, I find this problem in both scheduler and trigger, but when I look at airflow code, there is no gc job, which is strange. -- 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]
