Addshore added a subscriber: aaron. Addshore added a comment.
In T227758#5375986 <https://phabricator.wikimedia.org/T227758#5375986>, @Lucas_Werkmeister_WMDE wrote: > Usually, I believe MediaWiki guards against this with the ChronologyProtector, which saves the current replication position in the user’s session and waits until the replica selected for a request has at least caught up with that position. I don’t think that works very well cross-wiki; we could try to make it work, but it’s probably easier to duplicate its functionality client-side. As far as I know ChronologyProtector in RDBMS is setup to work with multiple dbs / connections so it might be fine to use this in some way. It would be worth checking with @aaron though. > One issue with that might be that the page could later be re-rendered again through the regular dispatch system, which would waste some server resources. We should check if dispatch has any checks built-in for whether a purge is necessary or not, and possibly add them. On the other hand, perhaps it’s not really a big deal? AFAIK there are currently no such checks. The parser output will have the TS of the parser / render. If the dispatching knows the time the change was made that it is dispatching for (not sure if it does) then a check could be performed. > Also, it would probably be good to investigate the ChronologyProtector a bit more instead of just writing it off as I did above :) sadly, it’s not really documented on mw.org. Yup TASK DETAIL https://phabricator.wikimedia.org/T227758 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Addshore Cc: aaron, Lucas_Werkmeister_WMDE, Addshore, Pablo-WMDE, Aklapper, Lydia_Pintscher, darthmon_wmde, DannyS712, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Wikidata-bugs, aude, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
