You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/04/26 10:57:55 UTC
[GitHub] [airflow] benyaa opened a new issue #15530: Could not get scheduler_job_id
benyaa opened a new issue #15530:
URL: https://github.com/apache/airflow/issues/15530
<!--
Welcome to Apache Airflow! For a smooth issue process, try to answer the following questions.
Don't worry if they're not all applicable; just try to include what you can :-)
If you need to include code snippets or logs, please put them in fenced code
blocks. If they're super-long, please use the details tag like
<details><summary>super-long log</summary> lots of stuff </details>
Please delete these comment blocks before submitting the issue.
-->
<!--
IMPORTANT!!!
PLEASE CHECK "SIMILAR TO X EXISTING ISSUES" OPTION IF VISIBLE
NEXT TO "SUBMIT NEW ISSUE" BUTTON!!!
PLEASE CHECK IF THIS ISSUE HAS BEEN REPORTED PREVIOUSLY USING SEARCH!!!
Please complete the next sections or the issue will be closed.
These questions are the first thing we need to know to understand the context.
-->
**Apache Airflow version**: 2.0.2
**Kubernetes version (if you are using kubernetes)** (use `kubectl version`): 1.20.2
**Environment**:
- **Cloud provider or hardware configuration**: Kubernetes
**What happened**: I tried to configure the scheduler, which runs in its own pod, to use the CeleryKubernetesExecutor, but it failed with the error "Could not get scheduler_job_id". I saw that it failed before with the KubernetesExecutor on its own and fixed.
If I set the executor to be KubernetesExecutor it initiates okay, if I set it to be CeleryExceutor it also initiates fine but it only happens when I use the CeleryKubernetesExecutor that it fails.
<!-- (please include exact error messages if you can) -->
**What you expected to happen**: The scheduler should have initiate successfully.
<!-- What do you think went wrong? -->
**How to reproduce it**: I guess it can be reproduced if you configure it to use this executor, I also use a custom pod template and redis as a celery broker so maybe it has something to do with this.
<!---
As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.
If you are using kubernetes, please attempt to recreate the issue using minikube or kind.
## Install minikube/kind
- Minikube https://minikube.sigs.k8s.io/docs/start/
- Kind https://kind.sigs.k8s.io/docs/user/quick-start/
If this is a UI bug, please provide a screenshot of the bug or a link to a youtube video of the bug in action
You can include images using the .md style of
To record a screencast, mac users can use QuickTime and then create an unlisted youtube video with the resulting .mov file.
--->
**Anything else we need to know**:
<!--
How often does this problem occur? Once? Every time etc? Every time
Any relevant logs to include? Put them here in side a detail tag:
<details><summary>x.log</summary> WARNING! You should run the image with GID (Group ID) set to 0
even if you use 'airflow' user (UID=50000)
You started the image with UID=50000 and GID=50000
This is to make sure you can run the image with an arbitrary UID in the future.
See more about it in the Airflow's docker image documentation
http://airflow.apache.org/docs/docker-stack/entrypoint
____________ _____________
____ |__( )_________ __/__ /________ __
____ /| |_ /__ ___/_ /_ __ /_ __ \_ | /| / /
___ ___ | / _ / _ __/ _ / / /_/ /_ |/ |/ /
_/_/ |_/_/ /_/ /_/ /_/ \____/____/|__/
[2021-04-26 10:57:11,733] {scheduler_job.py:1251} INFO - Starting the scheduler
[2021-04-26 10:57:11,734] {scheduler_job.py:1256} INFO - Processing each file at most -1 times
[2021-04-26 10:57:11,736] {kubernetes_executor.py:471} INFO - Start Kubernetes executor
[2021-04-26 10:57:11,736] {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
[2021-04-26 10:57:11,738] {dag_processing.py:453} WARNING - Ending without manager process.
[2021-04-26 10:57:11,738] {scheduler_job.py:1305} INFO - Exited execute loop </details>
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] boring-cyborg[bot] commented on issue #15530: Could not get scheduler_job_id
Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #15530:
URL: https://github.com/apache/airflow/issues/15530#issuecomment-826738340
Thanks for opening your first issue here! Be sure to follow the issue template!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] jedcunningham closed issue #15530: Could not get scheduler_job_id
Posted by GitBox <gi...@apache.org>.
jedcunningham closed issue #15530:
URL: https://github.com/apache/airflow/issues/15530
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [airflow] jedcunningham commented on issue #15530: Could not get scheduler_job_id
Posted by GitBox <gi...@apache.org>.
jedcunningham commented on issue #15530:
URL: https://github.com/apache/airflow/issues/15530#issuecomment-827192287
I wasn't able to replicate this in master. #13247 fixes this, but looks like it wasn't actually cherry picked into 2.0.1, so I'm going to move it into the 2.0.3 milestone so it lands in the next release.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org