Geo Frequently Asked Questions · Gitlab 中文文檔

# Geo Frequently Asked Questions > 原文：[https://docs.gitlab.com/ee/administration/geo/replication/faq.html](https://docs.gitlab.com/ee/administration/geo/replication/faq.html) * [What are the minimum requirements to run Geo?](#what-are-the-minimum-requirements-to-run-geo) * [How does Geo know which projects to sync?](#how-does-geo-know-which-projects-to-sync) * [Can I use Geo in a disaster recovery situation?](#can-i-use-geo-in-a-disaster-recovery-situation) * [What data is replicated to a **secondary** node?](#what-data-is-replicated-to-a-secondary-node) * [Can I `git push` to a **secondary** node?](#can-i-git-push-to-a-secondary-node) * [How long does it take to have a commit replicated to a **secondary** node?](#how-long-does-it-take-to-have-a-commit-replicated-to-a-secondary-node) * [What if the SSH server runs at a different port?](#what-if-the-ssh-server-runs-at-a-different-port) * [Is this possible to set up a Docker Registry for a **secondary** node that mirrors the one on the **primary** node?](#is-this-possible-to-set-up-a-docker-registry-for-a-secondary-node-that-mirrors-the-one-on-the-primary-node) # Geo Frequently Asked Questions[](#geo-frequently-asked-questions-premium-only "Permalink") ## What are the minimum requirements to run Geo?[](#what-are-the-minimum-requirements-to-run-geo "Permalink") 要求[在索引頁面](index.html#requirements-for-running-geo)上列出 ## How does Geo know which projects to sync?[](#how-does-geo-know-which-projects-to-sync "Permalink") 在每個**輔助**節點上，都有一個 GitLab 數據庫的只讀復制副本. **輔助**節點還具有跟蹤數據庫，其中存儲了已同步的項目. Geo 比較這兩個數據庫以查找尚未跟蹤的項目. 首先，此跟蹤數據庫為空，因此 Geo 將開始嘗試從它在 GitLab 數據庫中可以看到的每個項目中進行更新. 對于每個要同步的項目： 1. Geo 將發出`git fetch geo --mirror`來從**主**節點獲取最新信息. 如果沒有更改，則同步將很快并快速結束. 否則，它將提取最新的提交. 2. **輔助**節點將更新跟蹤數據庫，以存儲它已同步項目 A，B，C 等的事實. 3. 重復直到所有項目都同步. 當有人將提交推送到**主**節點時，它將在 GitLab 數據庫中生成一個事件，說明存儲庫已更改. **輔助**節點看到此事件，將有問題的項目標記為臟，并計劃重新同步該項目. 為確保管道問題（例如，同步失敗太多或丟失的作業）不會永久停止項目同步，Geo 還會定期檢查跟蹤數據庫中是否有標記為臟的項目. 當并發同步數降到`repos_max_capacity`以下并且沒有新的項目等待同步時，將進行此檢查. Geo 還具有校驗和功能，可在所有對 SHA 值的 Git 引用中運行 SHA256 和. 如果**主**節點和**輔助**節點之間的引用不匹配，則**輔助**節點會將項目標記為臟項目，然后嘗試重新同步. 因此，即使我們擁有一個過時的跟蹤數據庫，驗證也應激活并找到存儲庫狀態中的差異并重新同步. ## Can I use Geo in a disaster recovery situation?[](#can-i-use-geo-in-a-disaster-recovery-situation "Permalink") 是的，但是我們復制的內容有局限性（請參閱將[哪些數據復制到**輔助**節點？](#what-data-is-replicated-to-a-secondary-node) ）. 閱讀[災難恢復](../disaster_recovery/index.html)文檔. ## What data is replicated to a **secondary** node?[](#what-data-is-replicated-to-a-secondary-node "Permalink") 當前，我們復制項目存儲庫，LFS 對象，生成的附件/化身以及整個數據庫. 這意味著用戶帳戶，問題，合并請求，組，項目數據等將可用于查詢. ## Can I `git push` to a **secondary** node?[](#can-i-git-push-to-a-secondary-node "Permalink") 是! [GitLab Premium](https://about.gitlab.com/pricing/#self-managed) 11.3 中[引入](https://about.gitlab.com/releases/2018/09/22/gitlab-11-3-released/)了直接推送到**輔助**節點（對于 HTTP 和 SSH，包括 Git LFS）. ## How long does it take to have a commit replicated to a **secondary** node?[](#how-long-does-it-take-to-have-a-commit-replicated-to-a-secondary-node "Permalink") 所有復制操作都是異步的，并排隊等待分派. 因此，這取決于很多因素，包括流量，提交的大小，節點之間的連接，硬件等. ## What if the SSH server runs at a different port?[](#what-if-the-ssh-server-runs-at-a-different-port "Permalink") 很好我們使用 HTTP 來獲取從**主**節點到所有**輔助**節點的存儲庫更改. ## Is this possible to set up a Docker Registry for a **secondary** node that mirrors the one on the **primary** node?[](#is-this-possible-to-set-up-a-docker-registry-for-a-secondary-node-that-mirrors-the-one-on-the-primary-node "Permalink") 是. 有關[**輔助**節點，](docker_registry.html)請參見[Docker Registry](docker_registry.html) .