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.

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

CeleryKubernetesExecutor error: Could not get scheduler_job_id #16211

Closed
dstandish opened this issue Jun 2, 2021 · 1 comment
Closed

CeleryKubernetesExecutor error: Could not get scheduler_job_id #16211

dstandish opened this issue Jun 2, 2021 · 1 comment
Labels
area:Scheduler Scheduler or dag parsing Issues kind:bug This is a clearly a bug

Comments

@dstandish
Copy link
Contributor

Tried out CeleryKubernetesExecutor in apache chart 1.0.0 running on EKS

Official airflow image, python 3.8

Got this error in scheduler pod shortly after startup:

[2021-06-02 02:33:07,905] {kubernetes_executor.py:471} INFO - Start Kubernetes executor
[2021-06-02 02:33:07,905] {scheduler_job.py:1302} ERROR - Exception when executing SchedulerJob._run_scheduler_loop
Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/jobs/scheduler_job.py", line 1276, in _execute
    self.executor.start()
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/executors/celery_kubernetes_executor.py", line 60, in start
    self.kubernetes_executor.start()
  File "/home/airflow/.local/lib/python3.8/site-packages/airflow/executors/kubernetes_executor.py", line 473, in start
    raise AirflowException("Could not get scheduler_job_id")
airflow.exceptions.AirflowException: Could not get scheduler_job_id
@dstandish dstandish added the kind:bug This is a clearly a bug label Jun 2, 2021
@dstandish dstandish changed the title CeleryKubernetesExecutor error CeleryKubernetesExecutor error: Could not get scheduler_job_id Jun 2, 2021
@dstandish dstandish added the area:Scheduler Scheduler or dag parsing Issues label Jun 2, 2021
@jedcunningham
Copy link
Member

@dstandish, can we close this in favor of #16326? I assume this was with 2.0.2, and this specific problem doesn't happen in 2.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:Scheduler Scheduler or dag parsing Issues kind:bug This is a clearly a bug
Projects
None yet
Development

No branches or pull requests

2 participants