CeleryKubernetesExecutor jobs are not queued.
#293
Labels
kind/question
kind - user questions
Projects
Comments
jensgrnb
changed the title
CeleryKubernetesExecutor jobs are not queued on default queue id. CeleryKubernetesExecutor jobs are not queued.
|
@jensgrnb this issue is caused by airflow This apache/airflow#16700, has addressed the issue, and will be included in airflow |
thesuperzapper
moved this from Waiting for Response
to To Investigate
in Issue Triage and PR Tracking
|
Okay thanks for the reference! I'll be waiting eagerly for 2.1.2 then) Dodging meetings etc. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is your question?
I'm trying to get the
CeleryKubernetesExecutorup and running on our airflow cluster. I'm upgrading from aCeleryExecutorwhere the jobs are running fine, but when I simply upgrade the executor without adding anything, no jobs are queued at all.task instance details gives me
(the dependencies error is present when I only use
CeleryExecutoras well, but that doesn't stop the jobs from running fine.)the queue id for this job is
defaultand I was exepecting that this upgrade of executor would not affect anything at all, but instead everything grinds to a halt.Anyone experiencing similar issues? I'm on latest helm chart 8.4.0 and latest airflow 2-1-1-python3.8.
I've looked around for error logs on both the scheduler side and the worker side, but there's just nothing.
The text was updated successfully, but these errors were encountered: