Last modified: 2013-04-02 14:26:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T48715, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 46715 - Add a parameter to force read from master
Add a parameter to force read from master
Status: NEW
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.22.0
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-30 08:27 UTC by Liangent
Modified: 2013-04-02 14:26 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Liangent 2013-03-30 08:27:42 UTC
Sometimes my bot reads a page just after writing it due to people's commands. Because of database lag, it sometimes gets the old version, which confuses my bot.[1] In this case, a "force read from master" toggle might be useful.

[1] https://zh.wikipedia.org/w/index.php?title=User_talk:Liangent-bot&diff=next&oldid=25940295
Comment 1 Brad Jorsch 2013-03-30 13:37:13 UTC
IMO, it would be better for your bot to use maxlag=5 in its queries and to wait at least 5 seconds before re-reading the same page.
Comment 2 Liangent 2013-03-30 14:06:32 UTC
(In reply to comment #1)
> IMO, it would be better for your bot to use maxlag=5 in its queries and to
> wait
> at least 5 seconds before re-reading the same page.

Is it less expensive to process multiple repeated request than process one request from master?
Comment 3 Andre Klapper 2013-04-02 08:55:09 UTC
(In reply to comment #0)
> toggle might be useful.

=> severity = enhancement (feel free to set initially already)
Comment 4 Brad Jorsch 2013-04-02 14:21:35 UTC
(In reply to comment #2)
> Is it less expensive to process multiple repeated request than process one
> request from master?

I expect it's less expensive to process multiple repeated requests with maxlag than to have people abusing this to process lots of requests from master.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links