rjtshrm commented on issue #52501: URL: https://github.com/apache/airflow/issues/52501#issuecomment-3091478652
@ashb I didn't get what you meant by "I'm not sure your logic about CloudWatchRemoteLogIO.close being called is correct". Btw did you check the logs here: https://github.com/apache/airflow/issues/52501#issuecomment-3086500325. At the beginning of the logs you can see the trace and what leads to the the closing of Watchtower connection. You can reproduce the issue using the following steps: - Deploy Apache Airflow on Kubernetes: Use the official Helm Chart to deploy Airflow with - the Kubernetes executor. Use base airflow 3.0.3 with latest amazon provider installed. - Enable Remote Logging to CloudWatch Update your values.yaml with the following to enable CloudWatch-based remote logging - Use a Minimal DAG to Trigger the Behavior Refer to this comment for a minimal DAG that can trigger the issue: https://github.com/apache/airflow/issues/52501#issuecomment-3088946981 -- 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. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
