1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Hi!
- While no dedicated restart option exists, adding/removing/altering an arbitrary configuration override or log level option will force a restart.
Stopping an environment is not an option as there are numerous dependencies in Airflow such as the meta database that cannot be easily stopped. As an alternative, environments can be created and destroyed via API or CloudFormation.
- MWAA is running open source Airflow, either 1.10.12 or 2.0.2, and does not alter it's behavior. If the web server is not being updated to the lack of errors, it is likely that the scheduler responsible for serializing the DAGs has not completed or still sees errors. See your DAG processing logs in CloudWatch (may require INFO level logging). You can also debug locally using https://github.com/aws/aws-mwaa-local-runner
Thanks!
con risposta 3 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa