The maj_articles_recents table in the totoazero tool's database is not currently being replicated because the recent toolsdb crash caused a mismatch in some replicated data.
In order to restore replication, we will need to find time to shut down the tool and reimport it.
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| toolsdb: remove one of the temporary replication filters | operations/puppet | production | +0 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | • Bstorm | T253738 ToolsDB: master crashed, replica having consistency issues | |||
| Resolved | • Bstorm | T257273 Table for totoazero tool needs maintenance to prevent data loss |
maj_articles_recents table only contains few (less that a thousand) rows used by a script that runs four times a day, at 0h, 6h, 12h and 18h UTC, likely not running for more that one hour.
The table can safely be taken offline outside these hours. If you need one or two days of script off, don't hesitate to ask me.
But I don't think that there is need to "shut down the [entire] tool", as other scripts can run without this table.
Sorry, I need to circle back around to this. That should be enough information to get started on this particular table.
Mentioned in SAL (#wikimedia-cloud) [2020-07-30T19:56:37Z] <bstorm> Reimported the maj_articles_recents table on the replica and started replication again T257273
Change 617533 had a related patch set uploaded (by Bstorm; owner: Bstorm):
[operations/puppet@production] toolsdb: remove one of the temporary replication filters
Change 617533 merged by Bstorm:
[operations/puppet@production] toolsdb: remove one of the temporary replication filters