When we bumped to 1.7.1.3 we found that tasks would go into the new SCHEDULED state and get stuck there. We haven't determined why this happens.
We put a hacky patch into our scheduler that sets state to None for any tasks that are SCHEDULED at the beginning of the schedule loop. Name: airflow Version: 1.7.1.3 Name: celery Version: 3.1.23 Name: kombu Version: 3.0.35 redis_version:2.6.13 On Sun, Sep 4, 2016 at 6:34 AM, Bolke de Bruin <[email protected]> wrote: > Hi All, > > We have had some reports on this list and sometimes on Jira that the > scheduler sometimes seems to get stuck. I would like to track down this > issue, but until now much of the reporting has been a bit light on the > details. > > First and foremost I am assuming that getting “stuck” is only happening when > using a CeleryExecutor. To further track down the issue I would like to know > the following > > - Airflow version (pip show airflow) > - Celery version (pip show celery) > - Kombu version (pip show kombu) > > - Redis version (if applicable) > - RabbitMQ version (if applicable) > > - Sanitized airflow configuration > - Sanitized broker configuration > > If possible supply, preferably debug, logs of broker, scheduler and worker. > > Thanks! > Bolke >
