Geo Frequently Asked Questions
Can I use Geo in a disaster recovery situation?
There are limitations to what we replicate (see What data is replicated to a secondary node?). In an extreme data-loss situation you can make a secondary Geo into your primary, but this is not officially supported yet.
If you still want to proceed, see our step-by-step instructions on how to manually promote a secondary node into primary.
What data is replicated to a secondary node?
We currently replicate project repositories, LFS objects, generated
attachments / avatars and the whole database. This means user accounts,
issues, merge requests, groups, project data, etc., will be available for
query. We currently don't replicate artifact data (
Can I git push to a secondary node?
No. All writing operations (this includes
git push) must be done in your
How long does it take to have a commit replicated to a secondary node?
All replication operations are asynchronous and are queued to be dispatched in a batched request every 10 minutes. Besides that, it depends on a lot of other factors including the amount of traffic, how big your commit is, the connectivity between your nodes, your hardware, etc.
What if the SSH server runs at a different port?
We send the clone url from the primary server to any secondaries, so it
doesn't matter. If primary is running on port
2200, clone url will reflect