SelfLink: "/api/v1/namespaces/default/events/airflow-worker-549d57f499-2pjzw. Message: "Killing container with id docker://airflow-worker:Container failed liveness probe. Kubernetes Executor Kubernetes executor enables Airflow to scale very easily as the tasks run on. Usually, this error dagid could not be found happens because init container git sync wasn’t checkout from git repo. Uid: "c07a3081-a013-11e8-9038-42010a800056" Web server fetches job logs from each worker. You need to check logs from git-sync init container to make sure it was successfully checkout days. Looking at the stackdriver logs for GKE I see logs for the container being created, then started, then a bunch of these:įieldPath: "ntainers" LocalExecutor - Used mostly for playing around in the local machine. We are also seeing issues with the scheduler being stuck in a crash loop and having the workload suspended. Log folders Database There are different kinds of Executors one can use with Airflow. Metrics are collected through the Airflow StatsD plugin and sent to Datadogs DogStatsD. We are unable to use our composer environment at the moment because kubernetes is constantly restarting the worker pods. Executors: Open slots, queued tasks, running tasks, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |