GitHub user anavrotski added a comment to the discussion: FAB Provider - 'Server has gone away'
The captured pod logs don’t contain timestamps, so I can’t correlate them with the RDS server logs. I also can’t reproduce the installation of Airflow 3.1.8, because downgrading the database in this version fails and requires recreating the entire database. What I can add is that after installation, Airflow ran without issues for several hours and only then failed (in two separate environments). This error doesn’t appear when using the same database on the same cluster but with a different version of the FAB provider. So, let's close this issue as "unreproducible". Next time, when a new version of Airflow is released and it fails, I'll try to capture more info. P.S. Claude offered a long list of possible causes—Valkey cache tuning, Celery settings, and so on—for the “Task state changed externally” error. But the real root cause turned out to be simple: the API server was restarting because of a memory leak. GitHub link: https://github.com/apache/airflow/discussions/63718#discussioncomment-16157510 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
