If a page is watched my many users, then the UPDATE query should be batched. Currently this runs as a post-send update in idle-transaction mode. It shouldn't be to hard to add batching.
Description
Description
Details
Details
| 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 | |||
| Resolved | aaron | T134613 updateNotificationTimestamp() should batch queries | |||
| Resolved | Marostegui | T130067 Add wl_id to watchlist tables on production dbs | |||
| Resolved | jcrespo | T138810 Set databases as read-only or switchover to secondary datacenter | |||
| Resolved | Addshore | T125990 Add a wl_id field to the watchlist table | |||
| Resolved | Addshore | T160062 Allow setting the watchlist table to read-only on a per-wiki basis |
Event Timeline
Comment Actions
Change 287297 had a related patch set uploaded (by Aaron Schulz):
Batch updateNotificationTimestamp() UPDATE queries
Comment Actions
Change 290292 had a related patch set uploaded (by Umherirrender):
Batch updateNotificationTimestamp() UPDATE queries (without wl_id)
Comment Actions
Change 290292 merged by jenkins-bot:
Batch updateNotificationTimestamp() UPDATE queries (without wl_id)
Comment Actions
Change 287297 abandoned by Aaron Schulz:
[DNM] Make updateNotificationTimestamp() use the PK