@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.)
hq.recaptime.dev/wiki/Phorge
phorge
phabricator
1@title Managing Garbage Collection
2@group config
3
4Understanding and configuring garbage collection.
5
6Overview
7========
8
9Phorge generates various logs and caches during normal operation. Some of
10these logs and caches are usually of very little use after some time has
11passed, so they are deleted automatically (often after a month or two) in a
12process called "garbage collection".
13
14Garbage collection is performed automatically by the daemons. You can review
15all of the installed garbage collectors by browsing to {nav Config >
16Extensions/Modules > Garbage Collectors}.
17
18
19Configuring Retention Policies
20==============================
21
22You can reconfigure the data retention policies for most collectors.
23
24The default retention policies should be suitable for most installs. However,
25you might want to **decrease** retention to reduce the amount of disk space
26used by some high-volume log that you don't find particularly interesting, or
27to adhere to an organizational data retention policy.
28
29Alternatively, you might want to **increase** retention if you want to retain
30some logs for a longer period of time, perhaps for auditing or analytic
31purposes.
32
33You can review the current retention policies in
34{nav Config > Extensions/Modules > Garbage Collectors}. To change a policy,
35use `bin/garbage set-policy` to select a new policy:
36
37```
38phorge/ $ ./bin/garbage set-policy --collector cache.markup --days 7
39```
40
41You can use `--days` to select how long data is retained for. You can also use
42`--indefinite` to set an indefinite retention policy. This will stop the
43garbage collector from cleaning up any data. Finally, you can use `--default`
44to restore the default policy.
45
46Your changes should be reflected in the web UI immediately, and will take
47effect in the actual collector **the next time the daemons are restarted**.
48
49
50Troubleshooting
51===============
52
53You can manually run a collector with `bin/garbage collect`.
54
55```
56phorge/ $ ./bin/garbage collect --collector cache.general
57```
58
59By using the `--trace` flag, you can inspect the operation of the collector
60in detail.
61
62
63Next Steps
64==========
65
66Continue by:
67
68 - exploring other daemon topics with @{article:Managing Daemons with phd}.