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/02/13 22:53:28 UTC

[GitHub] [airflow] iainwo opened a new issue #14222: Scheduler Logging Unimplemented in Helm Chart with Airflow V2 & SequentialExecutor

iainwo opened a new issue #14222:
URL: https://github.com/apache/airflow/issues/14222


   ## Problem
   The helm chart does not implement a way for SequentialExecutor Airflow 2 deployments to serve logs; without using elasticsearch.
   
   ## Details
   Prior implementations utilize the CLI function `serve_logs`. This function has been deprecated as of v2.
   
   In `airflow/templates/scheduler/scheduler-deployment.yaml`:
   ```yaml
       181 {{- if and $local (not $elasticsearch) }}
       182         # Start the sidecar log server if we're in local mode and
       183         # we don't have elasticsearch enabled.
       184         - name: scheduler-logs
       185           image: {{ template "airflow_image" . }}
       186           imagePullPolicy: {{ .Values.images.airflow.pullPolicy }}
       187           args: ["serve_logs"]
   ```
   
   This will cause the helm deployment to break; and the scheduler will perpetually fail to start the `scheduler-logs` container inside of the scheduler deployment.
   
   Snippet from airflow [upgrade guide](https://airflow.apache.org/docs/apache-airflow/stable/upgrading-to-2.html).
   
   ```
   Remove serve_logs command from CLI
   
   The serve_logs command has been deleted. This command should be run only by internal application mechanisms and there is no need for it to be accessible from the CLI interface.
   ```
   
   ## Partial Solution
   Not sure how the non-elastic method for serving logs going forward.
   
   Astronomer branches yaml by:
   ```yaml
   {{- if semverCompare ">=1.10.12" .Values.airflowVersion }}
   ...
   {{- else }}
   ...
   {{- end }}
   ```


----------------------------------------------------------------
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] mik-laj commented on issue #14222: Scheduler Logging Unimplemented in Helm Chart with Airflow V2 & SequentialExecutor (serve_log)

Posted by GitBox <gi...@apache.org>.
mik-laj commented on issue #14222:
URL: https://github.com/apache/airflow/issues/14222#issuecomment-778766725


   Related: https://github.com/apache/airflow/issues/13331


----------------------------------------------------------------
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 #14222: Scheduler Logging Unimplemented in Helm Chart with Airflow V2 & SequentialExecutor

Posted by GitBox <gi...@apache.org>.
boring-cyborg[bot] commented on issue #14222:
URL: https://github.com/apache/airflow/issues/14222#issuecomment-778689604


   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] kaxil closed issue #14222: Scheduler Logging Unimplemented in Helm Chart with Airflow V2 & SequentialExecutor (serve_log)

Posted by GitBox <gi...@apache.org>.
kaxil closed issue #14222:
URL: https://github.com/apache/airflow/issues/14222


   


-- 
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