-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dag runs keep in running state (job not send to celery?) #860
Comments
Will you solve it? |
potiuk
added a commit
that referenced
this issue
Jan 19, 2021
* Adds automated user creation in the production image This PR implements automated user creation for the production image controlled by environment variables. This is a solution for anyone who would like to make a quick test of the production image and would like to: * init/upgrade the DB automatically * create a user This is particularly useful for internal SQLite db initialization but can also be used to initialize the user in docker-compose or similar cases where there is no equivalent of init containers that are usually used to perform the initialization. Closes #860
kaxil
pushed a commit
that referenced
this issue
Jan 21, 2021
* Adds automated user creation in the production image This PR implements automated user creation for the production image controlled by environment variables. This is a solution for anyone who would like to make a quick test of the production image and would like to: * init/upgrade the DB automatically * create a user This is particularly useful for internal SQLite db initialization but can also be used to initialize the user in docker-compose or similar cases where there is no equivalent of init containers that are usually used to perform the initialization. Closes #860 (cherry picked from commit bc026cf)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
My dag seem to stop running because active dags is reached.
If i go to the Dag Runs page then i see that there are 16 dag runs in the running state.
But they do not show up in celery.
After checking the airflow-scheduler logs i notice something odd but i do not know what to do.
First let me show you the logs for a good dag run:
Here we see that the run went to celery.
But if i now check a dag that is still in the running state:
We see here that 2 dags are being queued but there is no log about sending it to celery.
Does anyone know what is going on?
Thanks in advance!
Jordy
The text was updated successfully, but these errors were encountered: