- Issue created by @apaderno
- 🇪🇸Spain fjgarlin
The issue is nothing to do with the search, it's just that producing some uncached pages takes longer than 30 seconds sometimes, and then the 5xx gets cached.
The amount of seconds before showing a 5xx is set for all our infra. I don't know if we can tweak that per-project. I'll investigate.
Another option could be using something like https://www.drupal.org/project/warmer → , but I'm not sure that'll be enough.
- 🇮🇹Italy apaderno Brescia, 🇮🇹
Why is the 5xx error returned only in one out of three cases? Since the request is for the same documentation page, should not the error be returned in all the cases, or in none of the cases?
- 🇪🇸Spain fjgarlin
Good point. It might be posting to itself first and then doing the search. I've got some 5xx just loading https://api.drupal.org/api/drupal/core%21themes%21claro%21claro.theme/11.x, so if the page is pretty heavy, doing the search on top of it might trigger this.
I'm pretty sure that we can change the behaviour of the search.
- 🇪🇸Spain fjgarlin
I'll change priority to "major" so the "critical" issues are worked on first. Then this one.