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

   Closes: #32928
   
   A race condition occurs in the _adopt_completed_pods function when 
schedulers are running concurrently. _adopt_completed_pods function doesn't 
keep track of which scheduler went down so it constantly tries to adopt 
completed pods from normally working schedulers. On Airflow setups with 
concurrently running schedulers and with a lot of short living DAG's it leads 
to race condition and open slots leak. You can find detailed analysis of this 
situation in GitHub issue here 
(https://github.com/apache/airflow/issues/32928#issuecomment-1820413530) Even 
if one of the schedulers went down and left some pods in completed state it is 
not a big deal because: 
   1. Completed pods do not consume resources from kubernetes cluster 
   2. They can be deleted by airflow cleanup-pods CLI command which you can 
execute with the cronjob.
   
   Co-authored-by: Vlad Pastushenko [email protected]
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   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 an 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/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->


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