I think this works for us, thanks for the heads up.

Do you think the downtime should be announced to stakeholders? Wikitech being down seems like something some folks may want to know in advance.

In T272388#6758254, @aborrero wrote:

I think this works for us, thanks for the heads up.

Do you think the downtime should be announced to stakeholders? Wikitech being down seems like something some folks may want to know in advance.

Ideally sending an email to wikitech-l + User-notice tag should be enough, but I wanted to wait for the date/time confirmation, let's see if this time also works for @ssastry

Works for me. Tangentially, we are currently in process of possibly stopping all use of testreduce database for our tests and it is possible we might get it done by then as well.

Works for me. Tangentially, we are currently in process of possibly stopping all use of testreduce database for our tests.

In T272388#6758291, @ssastry wrote:

Works for me. Tangentially, we are currently in process of possibly stopping all use of testreduce database for our tests and it is possible we might get it done by then as well.

Oh sweet - in that case, please create a ticket so we can drop those databases :)

One small detail- I am unsure if labswiki use the proxy / has its failover service configured, due to it being handled by mediawiki, so for wikitech it may be a hard down (not only a read-only status). Please Marostegui confirm (I may have outdated info).

Correction, you already mentioned that on the body, ignore.

@jcrespo there is no active proxy for m5 - as I stated on the task there will be no reads and no writes.

Tech News might normally be a bit overkill for Wikitech being down for a couple of minutes (I'd recommend wikitech-l and a few short posts to a couple of technical wiki pages, in that case), but since there's already an item about Commons, we can just merge the two into one item and have this one tag along. It'll go out on Monday 25 January.

@Marostegui that timing sounds fine to me, especially if someone other than me (@Johan?) announces the downtime in advance.

In T272388#6760598, @Andrew wrote:

@Marostegui that timing sounds fine to me, especially if someone other than me (@Johan?) announces the downtime in advance.

I sent the email to wikitech-l and ops@ yesterday.
Regarding the banner, I will leave that up to @Johan to decide.

Thanks

To be very clear we're talking about the same thing, by "Wikitech" we're just referring to wikitech.wikimedia.org/wiki/ here and nothing else right?

Yes, that's it

I think the mailing lists and Tech News can be considered having announced it in advance. Were it a wiki seeing a lot of traffic, or we were expecting more than a couple of minutes of downtime, that might change things, but I think this should be enough for now.

In T272388#6760633, @Johan wrote:

I think the mailing lists and Tech News can be considered having announced it in advance. Were it a wiki seeing a lot of traffic, or we were expecting more than a couple of minutes of downtime, that might change things, but I think this should be enough for now.

agreed!

Added to the deployments calendar

Procedure:

Pre restart

• Silence m5 hosts
• buffer pool dump + disablement in advance to make the restart faster

Restart

• !log m5 master restart, wikitech will be unavailable - T272388
• set db1128 in RO
• db1128: restart mysql
• verify report_host is enabled
• verify read_only is OFF
• Once mysql is back: reload haproxy on dbproxy1021 (non active) and dbproxy1017 (non active)
• check everything is ok
• close this task

Pre-restart steps are done