[traceback] TimeoutExpired: remove_orphaned_files
Categories
(Tecken :: General, defect, P2)
Tracking
(Not tracked)
People
(Reporter: willkg, Assigned: relud)
Details
Attachments
(3 files)
Sentry: https://mozilla.sentry.io/issues/4723701783/events/642158414c5b4b79a185e3e6e1f2e574/
TimeoutExpired: Command '['python', '/app/manage.py', 'remove_orphaned_files', '--skip-checks']'
timed out after 60 seconds
Looks like the remove_orphaned_files takes longer than 60 seconds semi-regularly. As of now, there are 92 events of this in the last 30 days.
Before making any changes, we should add a timing metric to learn more about how long it takes to run and how often it hits the 60 second timeout. Then we should adjust the timeout value.
| Assignee | ||
Comment 1•2 years ago
|
||
| Assignee | ||
Comment 2•2 years ago
|
||
| Reporter | ||
Comment 3•2 years ago
•
|
||
This was deployed just now in bug #1880345 in v2024.02.14.
I verified that it's emitting data and we can see it in the "Time to remove orphaned files" panel.
| Assignee | ||
Comment 4•2 years ago
|
||
looking at when this occurs, it appears to have mostly stopped for a while after the january 9th deploy, then it picked up again on feb 1st, and stopped again with the feb 14th deploy. So I'm going to give this a month to start happening again before taking any further action.
| Assignee | ||
Comment 5•2 years ago
|
||
| Reporter | ||
Comment 6•2 years ago
|
||
I tweaked that graph so it knows the values are in milliseconds and thus gives the y-axis easier to think about labels. Does that change look right?
| Assignee | ||
Comment 7•2 years ago
|
||
that looks great! tyty
| Assignee | ||
Comment 8•2 years ago
|
||
there have been two timeouts in the last month, so we discussed it in the obs-team meeting and we're going to double the timeout, revisit in a month, and if it didn't work double the timeout again.
Comment 9•2 years ago
•
|
||
relud: Did the timeout get doubled? Another timeout error occured 2024-03-25, and it's still listing 60s as the timeout.
Edit: Interestingly, I don't see the 3 Sentry events that have occured in the last 30 days in the Grafana panel that exceeded the timeout. Everything looks to be below 55s? In the table for the graph data, the max is 53.5s.
| Assignee | ||
Comment 10•2 years ago
|
||
i have not updated the timeout, thank you for bringing it up, I will get on that right away.
grafana not showing timeouts: correct! if i understand correctly the timeout forcibly kills the process, so the metric cannot be emitted.
| Assignee | ||
Comment 11•2 years ago
|
||
| Assignee | ||
Comment 12•2 years ago
|
||
Comment 13•2 years ago
|
||
Ah okay that makes sense thanks. Cool; hopefully we stop seeing those errors with the increase. It will be interesting to see how much time over 60s these runs take.
| Assignee | ||
Comment 14•2 years ago
|
||
i archived the sentry issue "until escalating" so that we will notice that way if this issue needs to be revisited
| Reporter | ||
Comment 15•2 years ago
|
||
Timeout doubling was deployed to production just now in bug #1890798.
| Assignee | ||
Comment 16•2 years ago
|
||
resolving this until it reappears
| Assignee | ||
Comment 17•2 years ago
|
||
it reappeared, doubling again
| Assignee | ||
Comment 18•2 years ago
|
||
| Assignee | ||
Comment 19•2 years ago
|
||
marked the issue in sentry as "resolved in next release" now that we have release info
| Assignee | ||
Comment 20•2 years ago
|
||
relud merged PR [mozilla-services/tecken]: bug-1873752: double remove_orphaned_files timeout again (#2923) in d240c52.
Description
•