From b8a70c2c5d2c5fa559449632c53e677beb329ae8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rafa=C5=82=20Gajdulewicz?= Date: Thu, 16 Nov 2023 09:46:28 +0100 Subject: [PATCH] Fix replica count and links Fix the number of replicas + link to the actual gitserver deployment + point to S2 instead of sourcegraph.com --- .../departments/engineering/teams/source/how-gitserver-works.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/departments/engineering/teams/source/how-gitserver-works.md b/content/departments/engineering/teams/source/how-gitserver-works.md index 2f86fe3a6b3b..636cb4b315e3 100644 --- a/content/departments/engineering/teams/source/how-gitserver-works.md +++ b/content/departments/engineering/teams/source/how-gitserver-works.md @@ -32,7 +32,7 @@ One repository-related responsibility _not_ handled by gitserver is the scheduli ### Production instances -There are currently [20 gitserver instances](https://sourcegraph.com/github.com/sourcegraph/deploy-sourcegraph-cloud@ec7effbc9491e3ee0c77c3d70ac3f2eb8cb34837/-/blob/base/frontend/sourcegraph-frontend.Deployment.yaml?L104-105) in production on Sourcegraph Cloud. This is a static list made available via the `SRC_GIT_SERVERS` environment variable. +There are currently [10 gitserver instances](https://sourcegraph.sourcegraph.com/github.com/sourcegraph/deploy-sourcegraph-cloud@HEAD/-/blob/base/gitserver/gitserver.StatefulSet.yaml?L14) in production on sourcegraph.com. At the moment, we shard repositories across gitserver instances using a [modular hashing strategy](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@737e98fe5a1c329fd2b8f1366f931941042b5671/-/blob/internal/gitserver/client.go?L118-124) based on the repository name. This is the responsibility of the [gitserver client](https://sourcegraph.com/github.com/sourcegraph/sourcegraph@737e98fe5a1c329fd2b8f1366f931941042b5671/-/blob/internal/gitserver/client.go).