Thread history

From Support
Viewing a history listing
Jump to navigation Jump to search
Time User Activity Comment
11:58, 25 May 2015 Siebrand (talk | contribs) New reply created (Reply to 504 Gateway Time-out nginx)
11:56, 25 May 2015 Siebrand (talk | contribs) Summary changed  
16:39, 17 May 2015 Robin van der Vliet (talk | contribs) New reply created (Reply to 504 Gateway Time-out nginx)
16:23, 17 May 2015 Purodha (talk | contribs) New reply created (Reply to 504 Gateway Time-out nginx)
11:52, 17 May 2015 Nemo bis (talk | contribs) New reply created (Reply to 504 Gateway Time-out nginx)
11:43, 17 May 2015 Liuxinyu970226 (talk | contribs) Summary changed  
11:32, 17 May 2015 Purodha (talk | contribs) New thread created  

504 Gateway Time-out nginx

I got a "series of 504 Gateway Time-out"s during the recent minutes.

Purodha Blissenbach (talk)11:32, 17 May 2015

Server was overloaded at 13.38 CEST and got better by 13.41. I suggest to avoid doing expensive things like opening many tabs or using Special:SearchTranslations intensively. Can you defer your mass-reporting till after the translation rally?

Nemo (talk)11:52, 17 May 2015

I got two more such series, one is just over. Looks like Weekend-translation-rally-time :-)

Purodha Blissenbach (talk)16:23, 17 May 2015

I got the same error a few times.

 
 

I've closed this issue. The time-outs are related to a lack of server resources, mainly because ElastisSearch is enormously CPU hungry. We are in the process of requesting more computing resources from our hosting sponsor netcup.de. If we get the requested resources, we can upgrade our current installation to be much quicker...

Siebrand11:58, 25 May 2015