Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Executor reports task instance finished (failed) although the task says its queued. Was the task killed externally? #607

Open
stivenramireza opened this issue Nov 30, 2020 · 0 comments
Open

Executor reports task instance finished (failed) although the task says its queued. Was the task killed externally? #607

stivenramireza opened this issue Nov 30, 2020 · 0 comments

Comments

@stivenramireza
Copy link

stivenramireza commented Nov 30, 2020 •
edited

I have an airflow service running with CeleryExecutor with 4 workers. Currently I've got 15 DAGs. Recently I've tried to run another DAG and it fails. The error I got is: Executor reports task instance finished (failed) although the task says its queued. Was the task killed externally?

My DAG is stucked in the first task and it don't continue from it.

Psdata: This airflow service is currently running in a server with 8 GB Memory and 80 GB Disk. The memory has around 70% of its use.

What happened?

airflow
what happened
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stivenramireza