ephraimbuddy commented on issue #57618: URL: https://github.com/apache/airflow/issues/57618#issuecomment-3631307620
> One question on the proposed approach though: do you see any limitations or edge cases with using an optimistic locking strategy instead — by tightening the WHERE condition at write time — rather than introducing a pessimistic database lock to prevent concurrent scheduling? > > I’m curious whether an optimistic approach could sufficiently mitigate the race without the overhead and contention risks of DB-level locking. Are you saying that there is no possibility of having two schedulers picking the same TIs and both scheduling at the same time or a milliseconds apart? -- 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]
