dominikhei commented on PR #48121: URL: https://github.com/apache/airflow/pull/48121#issuecomment-2763458352
> This resolves occurrences of a second pod for me. However, I don't believe `startup_timeout_seconds` is suitable here, as it serves a different purpose, i.e., waiting for a pod to transition to running, whereas in this case we just need the pod to exist. > > startup_timeout_seconds could also be set to a particularly high value, for example in clusters where compute is provisioned on demand (in my case). Good note. We could either implement a default waiting time, > This resolves occurrences of a second pod for me. However, I don't believe `startup_timeout_seconds` is suitable here, as it serves a different purpose, i.e., waiting for a pod to transition to running, whereas in this case we just need the pod to exist. > > startup_timeout_seconds could also be set to a particularly high value, for example in clusters where compute is provisioned on demand (in my case). Thanks for the note, that something I didn't consider. Do you think a default wait time (e.g 60s) is the best approach here, or rather introduce a new parameter? -- 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]
