You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use airflow at work to handle a ton of our automated jobs (~50 in total). One of these jobs is a clean rebuild and test of the software. In airflow 2.9.3, I would periodically get a bad build due to writing errors, but didn't think much of it because they were so infrequent; I wrote this off as an overloaded NFS issue, which we sometimes have.
When I upgraded to 2.10.0, and also seeing this in 2.10.1, I'm seeing these much more frequently, nearly every time this job is run. For reference, the two types of error messages I'm seeing are:
make[2]: write error: stdout
and
/bin/sh: line 1: echo: write error: Resource temporarily unavailable
This is not the only job I'm seeing these errors on, I see them on a few others as well, though those jobs are doing less and this issue is happening to them less often. Any ideas on what I can do to reduce or ideally eliminate these?
I already tested this in a standalone instance and on much faster drives, but still seeing the same issue. Any help would be much appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I use airflow at work to handle a ton of our automated jobs (~50 in total). One of these jobs is a clean rebuild and test of the software. In airflow 2.9.3, I would periodically get a bad build due to writing errors, but didn't think much of it because they were so infrequent; I wrote this off as an overloaded NFS issue, which we sometimes have.
When I upgraded to 2.10.0, and also seeing this in 2.10.1, I'm seeing these much more frequently, nearly every time this job is run. For reference, the two types of error messages I'm seeing are:
and
This is not the only job I'm seeing these errors on, I see them on a few others as well, though those jobs are doing less and this issue is happening to them less often. Any ideas on what I can do to reduce or ideally eliminate these?
I already tested this in a standalone instance and on much faster drives, but still seeing the same issue. Any help would be much appreciated.
Beta Was this translation helpful? Give feedback.
All reactions