https://meta.wikimedia.org/wiki/Special:GlobalRenameProgress/MB has been stuck for nearly four days now. The rename on enwiki is stuck at "In progress" but doesn't seem to actually be progressing. All other wikis have been renamed successfully.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Increase retries for rename jobs | operations/puppet | production | +4 -1 |
Related Objects
Event Timeline
All three job retry attempts failed with a lock wait timeout (twice when changing usernames in page revisions, once on SELECT wl_user, wl_notificationtimestamp FROM watchlist WHERE wl_namespace = '2' AND wl_title = 'Mb66w' FOR UPDATE - how on Earth can you get lock contention on that?).
No idea. However it'd be good if in these cases the GlobalRenameProgress table showed a "failed" status instead of "in progress", which ain't true. Thanks.
Failed jobs are retried by the job queue; I'm not sure if there is a way for a job to tell that it has failed for the last time. Maybe renameuser_status could get a failure count column?
@aaron, any thoughts? Global rename cannot be made atomic (as it consists of a bunch of jobs running on a bunch of different wikis), can we increase the lock timeout somehow?
Maybe we can change the puppet config to bump the retry count for rename related jobs? E.g. in modules/mediawiki/templates/jobrunner/jobrunner.conf.erb .
Change 302650 had a related patch set uploaded (by Gergő Tisza):
Increase retries for rename jobs
Nope, a single case of failed rename in two weeks is not an emergency. This is a puppet patch so I can get it deployed in tomorrow's SWAT (or someone can just go on and merge it I guess). I'm working on fixing the affected account.
The global rename seemed to be finished so I reattached the enwiki account and deleted the status row. MB should be OK now.
User reported that they were able to log in. https://en.wikipedia.org/w/index.php?title=User_talk:K6ka&diff=733020609&oldid=732921752
I'm closing this since the issue with this rename is done and the task is specific to this. Should you disagree, feel free to reopen :)