Asquator commented on PR #54284: URL: https://github.com/apache/airflow/pull/54284#issuecomment-3170892613
Before going further, we have to agree on what behavior is desired for priorities. Today, it's a very demanding parameter which means: _Don't you dare looking at (max_tis+1)'th task unless you schedule the max_tis most prioritized ones_ The motivation for https://github.com/apache/airflow/pull/53492 was not to break this behavior. If we agree to give up this strict limitation, we can completely redesign priorities, and for that we have to find a new formal requirement which will always be satisfied. Are we ready to punish a highly-prioritized task and push it to the end of the list if it couldn't be scheduled for a moment because of some limit? -- 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]
