Skip to content

Commit 1d9e74d

Browse files
authored
docs: remove manual repo data purge section (#1104)
We now automatically reclaim disk space for deleted repos, and this debug endpoint no longer exists.
1 parent 3394998 commit 1d9e74d

File tree

1 file changed

+0
-17
lines changed

1 file changed

+0
-17
lines changed

docs/admin/how-to/remove-repo.mdx

Lines changed: 0 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -30,20 +30,3 @@ Alternately, if a repository is synced from multiple code host connections you m
3030
Open the repository's `Settings` page on Sourcegraph and from the `Mirroring` tab click `Reclone`.
3131

3232
![Reclone repository](https://storage.googleapis.com/sourcegraph-assets/docs/images/admin/how-to/reclone-repo.png)
33-
34-
## Manually purge deleted repository data from disk
35-
36-
After a repository is deleted from Sourcegraph in the database, its data still remains on disk on gitserver so that in the event the repository is added again it doesn't need to be recloned. These repos are automatically removed when disk space is low on gitserver. However, it is possible to manually trigger removal of deleted repos in the following way:
37-
38-
**NOTE:** This is not available on Docker Compose deployments.
39-
40-
1. Browse to Site Admin -> Instrumentation -> Repo Updater -> Manual Repo Purge
41-
2. You'll be at a url similar to `https://sourcegraph-instance/-/debug/proxies/repo-updater/manual-purge`
42-
3. You need to specify a limit parameter which specifies the upper limit to the number of repos that will be removed, for example: `https://sourcegraph-instance/-/debug/proxies/repo-updater/manual-purge?limit=1000`
43-
4. This will trigger a background process to delete up to `limit` repos, rate limited at 1 per second.
44-
45-
It's possible to see the number of repos that can be cleaned up on disk in Grafana using this query:
46-
47-
```
48-
max(src_repoupdater_purgeable_repos)
49-
```

0 commit comments

Comments
 (0)