| Vvjjkkii renamed this task from "Include Wikibase dispatch lag in API "maxlag" enforcing" to "1rcaaaaaaa". Vvjjkkii triaged this task as "High" priority. Vvjjkkii removed Ladsgroup as the assignee of this task. Vvjjkkii edited subscribers, added: Ladsgroup; removed: gerritbot, Aklapper. Vvjjkkii edited projects, added CheckUser, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), Tamil-Sites, Gamepress, Hashtags, JADE, KartoEditor, Language-2018-Apr-June, New-Editor-Experiences, Mail, TCB-Team; removed MW-1.32-release-notes (WMF-deploy-2018-07-10 (1.32.0-wmf.12)). Vvjjkkii updated the task description. (Show Details) |
CHANGES TO TASK DESCRIPTION
Per #wikimedia-hackathon-2018 discussion:
There should be a setting which maps the Wikidata dispatch lag to the API's max lag. This should be a set factor so that the max lag is determined by:
`maxLag = max( maxLag, WikibaseDispatchLag / DispatchLagToMaxLagFactor )` where `DispatchLagToMaxLagFactor` is probably `5` (which would mean bots stop at around 250s of dispatch lag) or `6` (which would make bots stop at 300s… if we were to do this, we should also make sure the respective alert is only fired at maybe 330s of dispatch lag).
This is similar to [[https://www.mediawiki.org/wiki/Manual:$wgJobQueueIncludeInMaxLagFactor|$wgJobQueueIncludeInMaxLagFactor]].
Note: This will need a hook in `ApiMain::getMaxLag` first. Alternatively Wikibase could overwrite `ApiMain::checkMaxLag` in its API subclasses… but that's probably the worse solution.26570726f6475636520796f757220627567207573696e67206120726563656e742076657273696f6e206f662074686520736f6674776172652c20746f2068652077696b6920636f6e74656e74206c616e67756167652e0a0a5468616e6b20796f752e0a546167730a436865636b557365720ad70a436f6e6e65637465642d4f70656e2d48657269746167652d42617463682d75706c6f61647320285241c42d4b4d425f315f323031372d3032290ad70a54616d696c2d53697465730ad70a47616d6570726573730ad70a48617368746167730ad70a4a4144450ad70a4b6172746f456469746f720ad70a4c616e67756167652d323031382d4170722d4a756e650ad70a4e65772d456469746f722d457870657269656e6365730ad70a4d61696c0ad70a5443422d5465616d0ad70a53756273637269626572730a4465736372697074696f6e20507265766965770a436f6e74656e77a6f6e652073657474696e6720696e20796f75722070726f66696c652c20636c69636b20746f207265636f6e63696c652e
There should be a setting which maps the Wikidata dispatch lag to the API's max lag. This should be a set factor so that the max lag is determined by:
`maxLag = max( maxLag, WikibaseDispatchLag / DispatchLagToMaxLagFactor )` where `DispatchLagToMaxLagFactor` is probably `5` (which would mean bots stop at around 250s of dispatch lag) or `6` (which would make bots stop at 300s… if we were to do this, we should also make sure the respective alert is only fired at maybe 330s of dispatch lag).
This is similar to [[https://www.mediawiki.org/wiki/Manual:$wgJobQueueIncludeInMaxLagFactor|$wgJobQueueIncludeInMaxLagFactor]].
Note: This will need a hook in `ApiMain::getMaxLag` first. Alternatively Wikibase could overwrite `ApiMain::checkMaxLag` in its API subclasses… but that's probably the worse solution.26570726f6475636520796f757220627567207573696e67206120726563656e742076657273696f6e206f662074686520736f6674776172652c20746f2068652077696b6920636f6e74656e74206c616e67756167652e0a0a5468616e6b20796f752e0a546167730a436865636b557365720ad70a436f6e6e65637465642d4f70656e2d48657269746167652d42617463682d75706c6f61647320285241c42d4b4d425f315f323031372d3032290ad70a54616d696c2d53697465730ad70a47616d6570726573730ad70a48617368746167730ad70a4a4144450ad70a4b6172746f456469746f720ad70a4c616e67756167652d323031382d4170722d4a756e650ad70a4e65772d456469746f722d457870657269656e6365730ad70a4d61696c0ad70a5443422d5465616d0ad70a53756273637269626572730a4465736372697074696f6e20507265766965770a436f6e74656e77a6f6e652073657474696e6720696e20796f75722070726f66696c652c20636c69636b20746f207265636f6e63696c652e
TASK DETAIL
EMAIL PREFERENCES
To: Vvjjkkii
Cc: Ladsgroup, pywikibot-bugs-list, ValterVB, Lea_Lacroix_WMDE, Legoktm, Addshore, MisterSynergy, Magnus, daniel, Anomie, Sjoerddebruin, Lydia_Pintscher, Multichill, hoo, AndyTan, Gaboe420, Zylc, Versusxo, Majesticalreaper22, Giuliamocci, Adrian1985, Cpaulf30, 1978Gage2001, Lahi, Gq86, Baloch007, Darkminds3113, Bsandipan, Lordiis, herron, pan199312, GoranSMilovanovic, lisong, Adik2382, Chicocvenancio, alanajjar, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Tbscho, LawExplorer, Lea_WMDE, Mattias_Ostmar-WMSE, Lewizho99, JJMC89, Maathavan, Jseddon, Ryuch, Mkdw, RuyP, JEumerus, Jonas, Trizek-WMF, KasiaWMDE, 0x010C, srodlund, Luke081515, grin, Bsadowski1, mys_721tx, Wikidata-bugs, Snowolf, aude, Huji, Gryllida, jayvdb, Ricordisamoa, Tobi_WMDE_SW, revi, scfc, He7d3r, Romaine, Mbch331, Jay8g, Glaisher, Krenair, chasemp, gerritbot, Aklapper
Cc: Ladsgroup, pywikibot-bugs-list, ValterVB, Lea_Lacroix_WMDE, Legoktm, Addshore, MisterSynergy, Magnus, daniel, Anomie, Sjoerddebruin, Lydia_Pintscher, Multichill, hoo, AndyTan, Gaboe420, Zylc, Versusxo, Majesticalreaper22, Giuliamocci, Adrian1985, Cpaulf30, 1978Gage2001, Lahi, Gq86, Baloch007, Darkminds3113, Bsandipan, Lordiis, herron, pan199312, GoranSMilovanovic, lisong, Adik2382, Chicocvenancio, alanajjar, Th3d3v1ls, Ramalepe, Liugev6, QZanden, Tbscho, LawExplorer, Lea_WMDE, Mattias_Ostmar-WMSE, Lewizho99, JJMC89, Maathavan, Jseddon, Ryuch, Mkdw, RuyP, JEumerus, Jonas, Trizek-WMF, KasiaWMDE, 0x010C, srodlund, Luke081515, grin, Bsadowski1, mys_721tx, Wikidata-bugs, Snowolf, aude, Huji, Gryllida, jayvdb, Ricordisamoa, Tobi_WMDE_SW, revi, scfc, He7d3r, Romaine, Mbch331, Jay8g, Glaisher, Krenair, chasemp, gerritbot, Aklapper
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
