| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| operations/mediawiki-config | master | +2 -2 | Use redis lock manager for dispatching in all production repo instances |
Details
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T108944 [Epic] Improve change dispatching | |||
| Resolved | • Ladsgroup | T151681 DispatchChanges: Avoid long-lasting connections to the master DB | |||
| Resolved | • Ladsgroup | T159826 Use redis-based lock manager in dispatch changes in production | |||
| Resolved | hoo | T159828 Use redis-based lock manager for dispatchChanges on test.wikidata.org |
Event Timeline
Comment Actions
The patch is there (https://gerrit.wikimedia.org/r/#/c/347395/) and I talked to Ops, It seems they are okay with merging it given it doesn't make too many requests to the redis nodes but it needs to be done after May 3rd due to the switchover.
Comment Actions
Change 347395 merged by jenkins-bot:
[operations/mediawiki-config@master] Use redis lock manager for dispatching in all production repo instances
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2017-05-08T11:14:32Z] <Amir1> start of ladsgroup@tin:/srv/mediawiki-staging$ scap sync-file wmf-config/Wikibase-production.php 'USe redis lockManager for change dispatching (T159826)'
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2017-05-08T11:15:21Z] <ladsgroup@tin> Synchronized wmf-config/Wikibase-production.php: USe redis lockManager for change dispatching (T159826) (duration: 00m 56s)