When editing a robot, is confronted with the following message, what is the problem? Pausing 300 seconds due to database server lag
On 13 February 2012 21:05, majid magidred@yahoo.com wrote:
When editing a robot, is confronted with the following message, what is the problem?
Pausing 300 seconds due to database server lag
There is no problem. The bot is pausing for 300 seconds because of database server lag.
Wikipedia (for instance) uses multiple database servers: one is the 'main' server, the others are 'slaves'. The 'main' server is the one that receives writes (e.g. page edits), the 'slaves' get this information from the main server.
When there are a lot of edits, there can be some lag between these, which is called 'database server lag'. To prevent this lag from building up, the site signals bots to slow down. This is what you are seeing.
Best, Merlijn
I found a server replication lag of 6000 seconds at the moment and I found the same for the last few days. This prevents bot from editing at all. Should we anyway enable editing for this long timout e.g. for one per minute or every 5 minutes or should bot edits always be blocked if the dbreplag is to high. An other idea would be not to prevent bot edits but just wait this time for the next edit.
Regards xqt
----- Original Nachricht ---- Von: Merlijn van Deen valhallasw@arctus.nl An: Pywikipedia discussion list pywikipedia-l@lists.wikimedia.org Datum: 13.02.2012 21:15 Betreff: Re: [Pywikipedia-l] problem
On 13 February 2012 21:05, majid magidred@yahoo.com wrote:
When editing a robot, is confronted with the following message, what is the problem?
Pausing 300 seconds due to database server lag
There is no problem. The bot is pausing for 300 seconds because of database server lag.
Wikipedia (for instance) uses multiple database servers: one is the 'main' server, the others are 'slaves'. The 'main' server is the one that receives writes (e.g. page edits), the 'slaves' get this information from the main server.
When there are a lot of edits, there can be some lag between these, which is called 'database server lag'. To prevent this lag from building up, the site signals bots to slow down. This is what you are seeing.
Best, Merlijn
Pywikipedia-l mailing list Pywikipedia-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikipedia-l
On 14 February 2012 13:48, info@gno.de wrote:
I found a server replication lag of 6000 seconds at the moment and I found the same for the last few days. This prevents bot from editing at all. Should we anyway enable editing for this long timout e.g. for one per minute or every 5 minutes or should bot edits always be blocked if the dbreplag is to high. An other idea would be not to prevent bot edits but just wait this time for the next edit.
No, you should complain in #wikimedia-tech or on wikitech-l about the high
replag. If the replication lag is high, *bots should stop editing*, as this will allow the replag to decrease.
See http://www.mediawiki.org/wiki/Manual:Maxlag_parameter
Best, Merlijn
2012/2/13 majid magidred@yahoo.com
When editing a robot, is confronted with the following message, what is the problem?
Pausing 300 seconds due to database server lag
I have just got this message, too, and it is very annoying when making a bot assisted manual spelling correction on several pages. The bot will namely not display the next page to correct until the lag is over. That's not the bot who is waiting and can't work, but me. Although we have put_async to do the human work faster and let the bot do the rest while we do something more useful, it is useless when my own work is stopped for five minutes.
2012/2/15 Bináris wikiposta@gmail.com
Updating page [[2011-es US Open (tenisz) - férfi páros]] via API Pausing 300 seconds due to database server lag. Updating page [[2011-es US Open (tenisz) - férfi páros]] via API Pausing 300 seconds due to database server lag. Updating page [[2011-es US Open (tenisz) - férfi páros]] via API Pausing 300 seconds due to database server lag. Updating page [[2011-es US Open (tenisz) - férfi páros]] via API Pausing 300 seconds due to database server lag. Updating page [[2011-es US Open (tenisz) - férfi páros]] via API ... Updating page [[2011-es wimbledoni teniszbajnokság - vegyes páros]] via API Updating page [[2008-as US Open (tenisz) - férfi páros]] via API Sleeping for 6.7 seconds, 2012-02-15 15:42:24 Updating page [[2009-es Roland Garros - férfi páros]] via API Updating page [[2009-es wimbledoni teniszbajnokság - vegyes páros]] via API Updating page [[Férfi egyes tenisz az 1996. évi nyári olimpiai játékokon]] via API Pausing 16 seconds due to database server lag. Updating page [[Férfi egyes tenisz az 1996. évi nyári olimpiai játékokon]] via API Pausing 33 seconds due to database server lag. Updating page [[Férfi egyes tenisz az 1996. évi nyári olimpiai játékokon]] via API Pausing 66 seconds due to database server lag. Updating page [[Férfi egyes tenisz az 1996. évi nyári olimpiai játékokon]] via API Pausing 133 seconds due to database server lag. Updating page [[Férfi egyes tenisz az 1996. évi nyári olimpiai játékokon]] via API Pausing 266 seconds due to database server lag. Updating page [[Férfi egyes tenisz az 1996. évi nyári olimpiai játékokon]] via API Pausing 300 seconds due to database server lag.
This *is* a problem in manual botwork. 20+13 minutes when I can neither continue nor close the window or switch off my computer or anything... And I am afraid some edits are simply lost.
On Wed, Feb 15, 2012 at 3:55 PM, Bináris wikiposta@gmail.com wrote:
This is a problem in manual botwork. 20+13 minutes when I can neither continue nor close the window or switch off my computer or anything... And I am afraid some edits are simply lost.
I guess there should be variation in replag waiting between various bots, with highly interactive bots not reacting at all, bots with less interaction only to severe server lag, and bots which are just switched on, then work interactively slowing down with even moderate server lag.
2012/2/15 Andre Engels andreengels@gmail.com
I guess there should be variation in replag waiting between various bots, with highly interactive bots not reacting at all, bots with less interaction only to severe server lag, and bots which are just switched on, then work interactively slowing down with even moderate server lag.
This sounds well. Replace.py could also detect the mode and go to sleep easier in automatic mode.
On 15 February 2012 19:43, Bináris wikiposta@gmail.com wrote:
2012/2/15 Andre Engels andreengels@gmail.com
I guess there should be variation in replag waiting between various bots, with highly interactive bots not reacting at all, bots with less interaction only to severe server lag, and bots which are just switched on, then work interactively slowing down with even moderate server lag.
This sounds well. Replace.py could also detect the mode and go to sleep easier in automatic mode.
I'd rather see less logic than more logic in bots - less code is less bugs. Instead, I'd like to propose a more general solution: a -config command line parameter that lets you override *any* configuration parameter in user-config.py/config.py, *including* maxlag.
Best, Merlijn