You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org

Depooling servers: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>MVernon
m (correct path to conftool data (node not nodes))
imported>Krinkle
No edit summary
Line 25: Line 25:
== mw* machines (and others) ==
== mw* machines (and others) ==


The mw* application servers and other servers managed via pybal/etcd are depooled by using conftool.
The mw* application servers and various other servers are managed by [[PyBal]] directly in Etcd. These can be controlled via [[conftool]] as well, including with the <code>depool</code> and <code>pool</code>utilities. This is documented at [[LVS#Etcd as a backend to Pybal (All of production)]].
This is documented at https://wikitech.wikimedia.org/wiki/LVS#Etcd_as_a_backend_to_Pybal_.28All_of_production.29
[[Category:How-To]]
[[Category:How-To]]
[[Category:Runbooks]]

Revision as of 02:54, 1 May 2022

Contains various ways to depool different servers. In a glorious future, we'd just need to do conftool depool <service> <node> but we aren't there yet!

cp*** machines

These are the varnish frontends, and should be depooled via conftool. To fully depool a server, do as root on any puppetmaster frontend:

confctl select dc=<dc>,cluster=<cluster-name>,name=cp*** set/pooled=no

You can find out <cluster-name> from looking at conftool-data/node/ in the operations/puppet repository.

An easier option is to ssh into the server and just run

$ sudo -i depool

To re-pool, run:

$ sudo -i pool

Note the use of sudo -i. depool needs environment variables to get access to etcd.

mw* machines (and others)

The mw* application servers and various other servers are managed by PyBal directly in Etcd. These can be controlled via conftool as well, including with the depool and poolutilities. This is documented at LVS#Etcd as a backend to Pybal (All of production).