Would it not be better to trial the switch over with the *.labsdb aliases
before risking catastrophic failure when rebooting? Doing a short test (up
to 24 hours) would allow users to identify anything that may break before
it becomes an unbreak now situation? If any critical systems are affected
the change can be rolled back, issues identified and fixed before the final
switch over.

On Wed, Oct 18, 2017 at 8:46 PM, Bryan Davis <[email protected]> wrote:

> The labsdb1001.eqiad.wmnet (aka c1.labsdb) and labsdb1003.eqiad.wmnet
> (aka c3.labsdb) servers are being shutdown and permanently removed
> from service on Wednesday 2017-12-13.
>
> TL;DR
>
> * Change your tools and scripts to use:
>   - "*.web.db.svc.eqiad.wmflabs" (real-time response needed)
>   - "*.analytics.db.svc.eqiad.wmflabs" (batch jobs; long queries)
> * Replace "*" with either a shard name (e.g. s1) or a wikidb name
>   (e.g. enwiki).
> * The new servers do not support user created databases/tables because
>   replication can't be guaranteed. See T156869 and below for more
>   information.
> * Migrate your user created tables to tools.db.svc.eqiad.wmflabs
>   (also known as tools.labsdb) and JOIN via application space logic
>   rather than in-process in the database.
>
> What is changing?
>
> * Week of 2017-10-30 to 2017-11-03 (exact date to be determined)
> ** Reboot labsdb1001.eqiad.wmnet (aka c1.labsdb) for kernel updates
> ** There is a possibility of catastrophic hardware failure in this
> reboot. There will be no way to recover the server or the data it
> currently hosts if that happens.
>
> * Week of 2017-11-06 to 2017-11-10 (exact date to be determined)
> ** Reboot labsdb1003.eqiad.wmnet (aka c3.labsdb) for kernel updates
> ** There is a possibility of catastrophic hardware failure in this
> reboot. There will be no way to recover the server or the data it
> currently hosts if that happens.
>
> * Wednesday 2017-12-13
> * "*.labsdb" service names switched to point at
> "*.web.db.svc.eqiad.wmflabs" equivalents.
> * User created tables will not be allowed on the new servers
> "c1.labsdb" and "c3.labsdb" point to.
> * labsdb1001.eqiad.wmnet removed from service.
> * labsdb1003.eqiad.wmnet removed from service.
>
>
> Why are we doing this?
>
> See <https://wikitech.wikimedia.org/wiki/Wiki_Replica_c1_and_c3_shutdown>
> and <https://phabricator.wikimedia.org/T142807> for a more complete
> description of the reasons for these changes.
>
>
> Bryan (on behalf of the Wikimedia Cloud Services and DBA teams)
> --
> Bryan Davis              Wikimedia Foundation    <[email protected]>
> [[m:User:BDavis_(WMF)]] Manager, Cloud Services          Boise, ID USA
> irc: bd808                                        v:415.839.6885 x6855
>
> _______________________________________________
> Wikimedia Cloud Services announce mailing list
> [email protected] (formerly
> [email protected])
> https://lists.wikimedia.org/mailman/listinfo/cloud-announce
> _______________________________________________
> Wikimedia Cloud Services mailing list
> [email protected] (formerly [email protected])
> https://lists.wikimedia.org/mailman/listinfo/cloud
_______________________________________________
Wikimedia Cloud Services mailing list
[email protected] (formerly [email protected])
https://lists.wikimedia.org/mailman/listinfo/cloud

Reply via email to