potiuk commented on PR #35473: URL: https://github.com/apache/airflow/pull/35473#issuecomment-1795475414
BTW. It's also possible that this test and dask executor integration has a bug or race condition. And yes I have a plan for that too. For now the hypothesis is it's just the contention - it used to happen in the past, then disappeared after some test optimisations, then appeared again - but by increasing the timeout and letting 500 or so jobs to run it and see if still occurs from time to time is just the easiest thing to do to verify this hypothesis. If it is wrong, without spending too much time on trying to understand dask executor details we will have no choice but to ask Dask community for help. We've been in the past reaching out to Dask community for dask executor problems (and sometimes they helped) and we might do it this time as ell asking them for help. This time however - after moving dask executor to provider - if we cannot quickly solve it ourselves we have simple mechanism. Since dask executor is now in provider, we can simply suspend the provider from being released. We have process for that, we've been doing that in the past for yandex and qubole. And if we still have flakiness problem with it and no solution at hand, I will propose suspending dask executor and reach out to dask community that without their help it will remain suspended - which will mean: - no tests run in main - only what's released as provider will be used in the future - no more PRS/fixes/dependency updates to the provider - no more `dask` extra in the next MINOR Ariflow release And until the flakiness problem is diagnosed and fixed by somoene (and run 100 or so PRs without showing the flakiness) we will not resume the provider. This will be my plan B if increasing timeout will not solve the problem. -- 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]
