Usiel opened a new pull request, #32709:
URL: https://github.com/apache/airflow/pull/32709
<!--
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:
How to write a good git commit message:
http://chris.beams.io/posts/git-commit/
-->
closes: https://github.com/apache/airflow/discussions/21243
This is my attempt at solving the issue raised in the linked discussion.
With this change we would introduce a new flag on `Pool`, that allows an admin
to decide whether to include tasks in deferred state in the pool open slot
calculation or not. By default we would not consider them, which mirrors the
current behavior.
As mentioned by various people on the discussion, having this as an option
can be quite useful, especially in cases where the system that is "shielded" by
the pool is not completely in the control of the developer. This allows us to
(mis)use pools as a rate-limiting device even when using the new deferrable
operators.
--
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]
