debian-mirror-gitlab/doc/administration/geo/replication/remove_geo_site.md

stage	group	info	type
Systems	Geo	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments	howto

Removing secondary Geo sites (PREMIUM SELF)

Secondary sites can be removed from the Geo cluster using the Geo administration page of the primary site. To remove a secondary site:

1. On the top bar, select Main menu > Admin.
2. On the left sidebar, select Geo > Nodes.
3. For the secondary site you want to remove, select Remove.
4. Confirm by selecting Remove when the prompt appears.

After the secondary site is removed from the Geo administration page, you must stop and uninstall this site. For each node on your secondary Geo site:

1. Stop GitLab:

   sudo gitlab-ctl stop
   

2. Uninstall GitLab:

   NOTE: If GitLab data has to be cleaned from the instance as well, see how to uninstall the Linux package and all its data.

   # Stop gitlab and remove its supervision process
   sudo gitlab-ctl uninstall
   
   # Debian/Ubuntu
   sudo dpkg --remove gitlab-ee
   
   # Redhat/Centos
   sudo rpm --erase gitlab-ee
   

When GitLab has been uninstalled from each node on the secondary site, the replication slot must be dropped from the primary site's database as follows:

1. On the primary site's database node, start a PostgreSQL console session:

   sudo gitlab-psql
   

   NOTE: Using gitlab-rails dbconsole does not work, because managing replication slots requires superuser permissions.

2. Find the name of the relevant replication slot. This is the slot that is specified with --slot-name when running the replicate command: gitlab-ctl replicate-geo-database.

   SELECT * FROM pg_replication_slots;
   

3. Remove the replication slot for the secondary site:

   SELECT pg_drop_replication_slot('<name_of_slot>');