• Data types
  • Git repositories
  • Blobs
  • Database
• Limitations on replication/verification
  • Replicated data types behind a feature flag
    • Enable or disable replication (for some data types)
    • Limitation of verification for files in Object Storage

Geo data types support

A Geo data type is a specific class of data that is required by one or more GitLab features to store relevant information.

To replicate data produced by these features with Geo, we use several strategies to access, transfer, and verify them.

Data types

We currently distinguish between three different data types:

• Git repositories
• Blobs
• Database

See the list below of each feature or component we replicate, its corresponding data type, replication, and verification methods:

• (1): Redis replication can be used as part of HA with Redis sentinel. It’s not used between Geo sites.
• (2): Object storage replication can be performed by Geo or by your object storage provider/appliance native replication feature.

Git repositories

A GitLab instance can have one or more repository shards. Each shard has a Gitaly instance that is responsible for allowing access and operations on the locally stored Git repositories. It can run on a machine with a single disk, multiple disks mounted as a single mount-point (like with a RAID array), or using LVM.

It requires no special file system and can work with NFS or a mounted Storage Appliance (there may be performance limitations when using a remote file system).

Communication is done via Gitaly’s own gRPC API. There are three possible ways of synchronization:

• Using regular Git clone/fetch from one Geo site to another (with special authentication).
• Using repository snapshots (for when the first method fails or repository is corrupt).
• Manual trigger from the Admin Area (a combination of both of the above).

Each project can have at most 3 different repositories:

• A project repository, where the source code is stored.
• A wiki repository, where the wiki content is stored.
• A design repository, where design artifacts are indexed (assets are actually in LFS).

They all live in the same shard and share the same base name with a -wiki and -design suffix for Wiki and Design Repository cases.

Besides that, there are snippet repositories. They can be connected to a project or to some specific user. Both types will be synced to a secondary site.

Blobs

GitLab stores files and blobs such as Issue attachments or LFS objects into either:

• The file system in a specific location.
• An Object Storage solution. Object Storage solutions can be:
  • Cloud based like Amazon S3 Google Cloud Storage.
  • Hosted by you (like MinIO).
  • A Storage Appliance that exposes an Object Storage-compatible API.

When using the file system store instead of Object Storage, you need to use network mounted file systems to run GitLab when using more than one node.

With respect to replication and verification:

• We transfer files and blobs using an internal API request.
• With Object Storage, you can either:
  • Use a cloud provider replication functionality.
  • Have GitLab replicate it for you.

Database

GitLab relies on data stored in multiple databases, for different use-cases. PostgreSQL is the single point of truth for user-generated content in the Web interface, like issues content, comments as well as permissions and credentials.

PostgreSQL can also hold some level of cached data like HTML rendered Markdown, cached merge-requests diff (this can also be configured to be offloaded to object storage).

We use PostgreSQL’s own replication functionality to replicate data from the primary to secondary sites.

We use Redis both as a cache store and to hold persistent data for our background jobs system. Because both use-cases have data that are exclusive to the same Geo site, we don’t replicate it between sites.

Elasticsearch is an optional database, that can enable advanced searching capabilities, like improved Advanced Search in both source-code level and user generated content in Issues / Merge-Requests and discussions. Currently it’s not supported in Geo.

Limitations on replication/verification

The following table lists the GitLab features along with their replication and verification status on a secondary site.

You can keep track of the progress to implement the missing items in these epics/issues:

• Geo: Build a scalable, self-service Geo replication and verification framework
• Geo: Improve the self-service Geo replication framework
• Geo: Move existing blobs to framework
• Geo: Add unreplicated data types
• Geo: Support GitLab Pages

Replicated data types behind a feature flag

The replication for some data types is behind a corresponding feature flag:

• They’re deployed behind a feature flag, enabled by default.
• They’re enabled on GitLab.com.
• They can’t be enabled or disabled per-project.
• They are recommended for production use.
• For GitLab self-managed instances, GitLab administrators can opt to disable them.

Enable or disable replication (for some data types)

Replication for some data types are released behind feature flags that are enabled by default. GitLab administrators with access to the GitLab Rails console can opt to disable it for your instance. You can find feature flag names of each of those data types in the notes column of the table below.

To disable, such as for package file replication:

Feature.disable(:geo_package_file_replication)

To enable, such as for package file replication:

Feature.enable(:geo_package_file_replication)

Limitation of verification for files in Object Storage

GitLab managed Object Storage replication support is in beta.

Locally stored files are verified but remote stored files are not.