You are browsing a read-only backup copy of Wikitech. The primary site can be found at

Switch Datacenter

From Wikitech-static
Revision as of 20:44, 9 March 2016 by imported>Jcrespo (→‎MediaWiki-related: Database overview steps)
Jump to navigation Jump to search


A datacenter switchover (from eqiad to codfw, or vice-versa) comprises switching over multiple different components, some of which can happen independently and many of which need to happen in lockstep. This page documents all the steps needed to switch over from a master datacenter to another one, broken up by component.

Schedule for Q3 FY2015-2016 rollout

  • Deployment server: Jan 20th
  • Media storage/Swift: March 10th
  • Traffic: Mar 10th
  • ElasticSearch:
  • Services:
  • MediaWiki: March 22nd (fallback: April 18th)

Per-service switchover instructions


Before switch over (after any local testing within codfw):

  • Wipe memcached to prevent stale values (MediaWiki isn't ready for Multi-DC yet).
    • Once eqiad is read-only and cofdw read-only master/slaves are caught up; any subsequent requests to codfw that set memcached are fine.

The overall plan for an eqiad->codfw switchover is:

  • Warmup codfw databases
  • Warming up memcached with parsercache entries
  • Deploy mediawiki-config with all shards set to read-only
  • Set eqiad databases (masters) in read-only mode; stop pt-heartbeat (?)
  • Redis failover
  • Deploy Varnish to switch backend to appserver.svc.codfw.wmnet/api.svc.codfw.wmnet
  • Deploy services to change their MediaWiki action API endpoint
    • RESTBase (uses puppet's $mw_primary, needs puppet run + service restart)
    • Parsoid (manages its own config, will need a deploy + restart of its own)
    • Mobileapps (no manual intervention needed)
  • Master swap for every core (s1-7), ES (es1-3), parsercache (pc) and External store (x1) database
    • Technically there is nothing to do at database level once circular replication is setup
    • In reality, some small deploys: set codfw masters mysql as read-write and start pt-heartbeat-wikimedia there; change *-master dns to the new masters (only used by humans); optionally: puppetize $master = true
  • Deploy mediawiki-config (only codfw?) with all shards set to read-write

The plan for switching back is the reverse of the above, with the following extra step:

  • Wipe memcached to clear invalidated cached memory


See the separate page on how to promote a new slave to master.

Job queue

The following subsystems have their switchover depending on the puppet variable $mw_primary and thus depend on puppet for the actual switchover


You can force Varnish to pass a request to a backend in CODFW or EQIAD using the X-Wikimedia-Debug header.

For CODFW, use X-Wikimedia-Debug: backend=mw2017.codfw.wmnet

For EQIAD, use X-Wikimedia-Debug: backend=mw1017.eqiad.wmnet

Media storage/Swift


  • Instruct mediawiki to write synchronously to both eqiad/codfw with
  • Change varnish backends for app swift in hieradata/common/cache/upload.yaml to point to codfw
  • Change route_table in hieradata/role/common/cache/upload.yaml so that codfw is direct.
  • Change route_table in hieradata/role/common/cache/upload.yaml so that eqiad points to codfw.


  • Point swift rewrite middleware to codfw with and run puppet on ms-fe* plus swift-init all reload for the changes to take effect. Now 404s for thumbs will hit codfw imagescalers.
  • Change varnish backends for app rendering in hieradata/common/cache/text.yaml to point to codfw
  • Change varnish backends for app swift_thumbs in hieradata/common/cache/upload.yaml to point to codfw, user traffic for thumbs hits swift codfw



GeoDNS user routing

Inter-Cache routing

Cache->App routing


  • RESTBase and Parsoid already active in codfw, using eqiad MW API.
  • Shift traffic to codfw:
    • Public traffic: Update Varnish backend config.
    • Update RESTBase and Flow configs in mediawiki-config to use codfw.
  • During MW switch-over:

Other miscellaneous