Not only each update took 25 seconds, which is a lot, no wait for lag was executed between each execution (or it didn't work as intended) because otherwise no lag would have been created.
Unlike lag in other servers, which just would be depooled, I think this is a high impacting one, as specific roles are not ignored on lag.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Declined | None | T3268 Database replication lag issues (tracking) | |||
| Duplicate | None | T108551 Database locked error while publishing article using CX | |||
| Resolved | aaron | T95501 Fix causes of replica lag and get it to under 5 seconds at peak | |||
| Duplicate | None | T141340 /* RenameUserJob::run */ of user Burgundo created >1000 seconds of lag on itwiki (db1036), impacting recentchanges, watchlist and log visualization of all s2 wikis |