hkc-8010 commented on issue #64213: URL: https://github.com/apache/airflow/issues/64213#issuecomment-4150540258
Following up after additional investigation: I no longer think this issue represents a confirmed Airflow source-code bug in `S3KeySensor` / the amazon provider. What changed: - I re-tested `S3KeySensor` in deferrable mode and it worked correctly when the AWS connection credentials were valid and formatted correctly. - I also correlated the original customer incident with the wider deployment state and found significant triggerer instability during the same window, including repeated `Response read out of order`, `Process exited abnormally exit_code=126`, and `Trigger runner process has died! Exiting.` across multiple triggerer pods. - The original report also overlapped with very aggressive triggerer tuning / resource pressure in that deployment, which is a more likely explanation for the observed behavior than a deterministic source-code defect in the sensor itself. So at this point, I do not have a clean upstream repro that isolates an Airflow bug in the provider or sensor code. The earlier issue body was based on an incomplete investigation that over-indexed on the task-local connection symptom before ruling out deployment-level instability. Closing this issue to avoid leaving a misleading bug report open. If I can later produce a minimal, deployment-independent repro that demonstrates a real triggerer / Task SDK defect in upstream Airflow, I can open a new issue with that narrowed reproduction. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
