Added with https://meta.wikimedia.org/w/index.php?title=Tech/News/2019/15&diff=18991805&oldid=18990102

Thanks very much!

In T220080#5087526, @Marostegui wrote:

Thanks very much!

@Marostegui - Is it the 10th or 11th? You've said 10th in the email but 11th on here. Linked task says Wednesday 11th as well.

It is the 11th, sorry!
I will amend my email, thanks for noticing

@Marostegui - No problem

I've created a message and asked for translations, and will send it out on Monday, which is also when the Tech News issue including this will go out. I've also pinged @Trizek-WMF to see if we could add another banner warning people ahead of time.

(I almost missed I had been subscribed to this – too many Phab notifications sometimes. We'll normally pay attention to wikitech-l and notice if there's an upcoming read-only period, of course, but I'd recommend sending an email to us pinging us about a support request be on the safe side if it's time-sensitive.)

Thanks @Johan! Any preferred email address for next time?

Our team support email address is probably the safest way to get our attention if something is important and urgent, so it doesn't risk getting lost because one person is out of office or too swamped with other work.

Thank you, we'll do that next time too!

A MassMessage has been delivered to the wikis.

Just to confirm, Wikidata is not impacted, right?

Wikidata itself, and the top most visited wikipedias, meta, commons, centralauth, etc. will not be impacted. However, if wikidata changes something that would result on changes to the s3 local databases, those won't go through during the maintenance. What that means, if they will be retried or aborted, will depend on how Wikibase responds to the read only time on client wikis. I think Amir did monitor the effects last time (T213858) and there was not huge issues, but please ask him if he has any input. Maybe you may want to do something to prevent stale info? I don't know.

The following wikis can't be targeted by a CentralNotice banner. They have to be messaged to setup a banner if needed.

• wikimedia
• noboard_chapters
• wikimania
• arbcom
• otrs
• advisors
• advisory
• auditcom
• board
• boardgovcom
• chair
• chapcom
• checkuser
• collab
• donate
• electcom
• exec
• fdc
• fixcopyright
• foundation
• grants
• iegcom
• incubator
• internal
• legalteam
• login
• movementroles
• nostalgia
• office
• ombudsmen
• outreach
• projectcom
• quality
• searchcom
• steward
• strategy
• techconduct
• ten
• test
• test2
• transitionteam
• usability
• vote

In T220080#5093222, @Lea_Lacroix_WMDE wrote:

Just to confirm, Wikidata is not impacted, right?

test.wikidata is impacted.

I don't think the listed wikis need a banner.

Banner set for Wikipedias.
Other wikis will be set tomorrow.

In T220080#5093287, @jcrespo wrote:

Wikidata itself, and the top most visited wikipedias, meta, commons, centralauth, etc. will not be impacted. However, if wikidata changes something that would result on changes to the s3 local databases, those won't go through during the maintenance. What that means, if they will be retried or aborted, will depend on how Wikibase responds to the read only time on client wikis. I think Amir did monitor the effects last time (T213858) and there was not huge issues, but please ask him if he has any input. Maybe you may want to do something to prevent stale info? I don't know.

Yes, this will affect change dispatching of Wikidata. Last time it was for a few minutes but this one is for half an hour which means probably failed jobs will go to retry and pile up and bring down the whole jobqeue (probably bringing down everything with themselves including all wikis). I suggest disabling change dispatching totally for the period of downtime.

@Ladsgroup, should I display the banner on Wikidata as well, then?

In T220080#5094998, @Trizek-WMF wrote:

@Ladsgroup, should I display the banner on Wikidata as well, then?

Editing won't be disabled on wikidata and disabling it would cause issues in other wikis (for example, in case of a page move in enwiki, that wouldn't reach wikidata). We can have a different banner asking user to not edit to reduce the load when everything is back to normal

The window is for 30 minutes, but if all goes fine we are expecting it to take 4-5 minutes tops

In T220080#5095193, @Marostegui wrote:

The window is for 30 minutes, but if all goes fine we are expecting it to take 4-5 minutes tops

Then disabling change dispatching won't make much sense. I can stay around to monitor.

More concrete numbers from the last failover of this same section: T213858#4887175
03:20 minutes of read only, we hope to be around that number if all goes as planned

I'll be at a conference tomorrow; if anything specific would require our attention, @Whatamidoing-WMF will be around late afternoon/evening UTC.

Done for banners.

Thank you!