stage | group | info |
---|---|---|
Systems |
Geo |
To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments |
DETAILS: Tier: Premium, Ultimate Offering: Self-managed
Secondary sites can be removed from the Geo cluster using the Geo administration page of the primary site. To remove a secondary site:
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:
Stop GitLab:
sudo gitlab-ctl stop
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:
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.
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;
Remove the replication slot for the secondary site:
SELECT pg_drop_replication_slot('<name_of_slot>');
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。