{"id":4997,"date":"2020-05-26T08:09:31","date_gmt":"2020-05-26T06:09:31","guid":{"rendered":"https:\/\/www.almtoolbox.com\/blog\/?p=4997"},"modified":"2020-05-28T17:25:08","modified_gmt":"2020-05-28T15:25:08","slug":"gitlab-13-0-improved-high-availability","status":"publish","type":"post","link":"https:\/\/www.almtoolbox.com\/blog\/gitlab-13-0-improved-high-availability\/","title":{"rendered":"New in GitLab Version 13.0: GitLab Introduces Improved High Availability (HA)"},"content":{"rendered":"

\"gitlab<\/p>\n

GitLab version 13.0, released just days ago, now allows for high availability<\/em> and redundancy of the Git storage component.
\n<\/span>This is important if GitLab is critical<\/em> <\/strong>for your organization, and its downtime disables software development, CI\/CD pipelines and delivery times.<\/span><\/p>\n

We are talking about Gitaly —<\/em>\u00a0one of GitLab\u2019s most important components.<\/span><\/p>\n

Let’s talk about Gitaly<\/span><\/h3>\n

Gitaly is an open-source service, which enables RPC-based fast read\/write to git repositories without a need in NFS (Network File System).<\/span><\/p>\n

Previously, the GitLab HA model did not include redundancy of the git storage. The new Gitaly Clusters feature fills that void.<\/span><\/p>\n

Gitaly Cluster<\/h3>\n

A Gitaly Cluster contains several Gitaly nodes, where every git repository is stored on every node in the cluster. If an outage occurs on one node, another takes over.<\/span><\/p>\n

This improvement is another step toward a complete active-active cluster solution.<\/span><\/p>\n

We have already experimented and seen running results on an early version of this feature and the results look satisfactory!<\/span><\/p>\n

So what does the new feature give you?<\/h3>\n