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

Depooling servers: Difference between revisions

From Wikitech-static
Jump to navigation Jump to search
imported>Giuseppe Lavagetto
m (Correct confctl syntax, reference to palladium)
imported>Krinkle
No edit summary
Line 19: Line 19:
The mw* application servers and other servers managed via pybal/etcd are depooled by using conftool.
The mw* application servers and other servers managed via pybal/etcd are depooled by using conftool.
This is documented at https://wikitech.wikimedia.org/wiki/LVS#Etcd_as_a_backend_to_Pybal_.28All_of_production.29
This is documented at https://wikitech.wikimedia.org/wiki/LVS#Etcd_as_a_backend_to_Pybal_.28All_of_production.29
[[Category:How-To]]

Revision as of 22:33, 3 May 2018

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/nodes/ in the operations/puppet repository.

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

$ depool

mw* machines (and others)

The mw* application servers and other servers managed via pybal/etcd are depooled by using conftool. This is documented at https://wikitech.wikimedia.org/wiki/LVS#Etcd_as_a_backend_to_Pybal_.28All_of_production.29