SelfLink: "/api/v1/namespaces/default/events/airflow-worker-549d57f499-2pjzw. Logs of tasks when running is not available with kubernetesexecutor on webserver UI 20779 Closed 1 of 2 tasks nirutgupta opened this issue on 5 comments nirutgupta commented on name: AIRFLOWLOGGINGLOGGINGCONFIGCLASS value: 'logconfig. Message: "Killing container with id docker://airflow-worker:Container failed liveness probe. Looking at the stackdriver logs for GKE I see logs for the container being created, then started, then a bunch of these:įieldPath: "ntainers" the information added to kubernetes executor logs for better traceability logstaskmetadata. The only very annoying issue is despite all my attempt I cannot have 'live' logging of my running dags. This is the template for Airflows default configuration. With some bad patch/ manual tweaking it works more or less. This happens even when there are no DAGs executing on the cluster.Ĭ:\Users\Ben\AppData\Local\Google\Cloud SDK>kubectl get podsĪirflow-scheduler-f4d6476b5-qrjz8 2/2 Running 111 11hĪirflow-sqlproxy-9f9488c95-fnpjd 1/1 Running 8 16dĪirflow-webserver-6679f6447f-s742s 2/2 Running 16 15hĪirflow-worker-549d57f499-2pjzw 2/2 Running 1276 16dĪirflow-worker-549d57f499-bhk25 2/2 Running 1359 16dĪirflow-worker-549d57f499-cp47x 2/2 Running 18 11hĪirflow-worker-549d57f499-sznwf 2/2 Running 18 13h on Mar 1 Apache Airflow version 2.5.1 What happened I use kubernetes executor. We are also seeing issues with the scheduler being stuck in a crash loop and having the workload suspended. We are unable to use our composer environment at the moment because kubernetes is constantly restarting the worker pods.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |