keith991001 commented on issue #73196: URL: https://github.com/apache/airflow/issues/73196#issuecomment-5691451231
This decoupling makes sense to me — one knob spanning three components with different heartbeat/health-check budgets forces exactly the kind of lockstep tuning you describe. If you're not already planning to implement it yourself, I'd be happy to pick it up: add `[triggerer]` / `[dag_processor]` overrides that fall back to the current `[workers]` values for backwards compatibility, wire them where each component builds its API client retry policy, and cover the fallback semantics with tests. And if you'd rather drive it, I'm glad to help review instead. --- Drafted-by: Claude Code (Fable 5); reviewed by @keith991001 before posting -- 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]
