Files
nomad/website/content/docs/commands/system/gc.mdx
Aimee Ukasick 23fd87d9c9 Docs: Commands section move "General options" to page bottom (#26001)
* sectionless files plus acl section

* alloc section

* config, deployment sections

* job section

* licence, namespace

* node, node-pool

* operator

* plugin, quota, recommendation

* scaling, sentinel, server, service, system, var, volume

* Add "ENT" label to left nav for enterprise commands

* job tag break into separate folder and files; update options header
2025-06-12 14:31:38 -05:00

47 lines
1.5 KiB
Plaintext

---
layout: docs
page_title: 'nomad system gc command reference'
description: |
The `nomad system gc` command runs the system garbage collection process on jobs, evaluations, allocations, and nodes.
---
# `nomad system gc` command reference
Initializes a garbage collection of jobs, evaluations, allocations, and nodes.
This is an asynchronous operation.
Nomad periodically garbage collects jobs, evaluations, allocations, and nodes.
The exact garbage collection logic varies by object, but in general Nomad only
permanently deletes objects once they are terminal and no longer needed for
future scheduling decisions. See [`gc` related server agent configuration
parameters][gc_params] for details on tuning periodic garbage collection.
[gc_params]: /nomad/docs/configuration/server#node_gc_threshold
The `system gc` command bypasses these settings and immediately attempts to
garbage collect dead objects regardless of any "threshold" or "interval" server
settings. This is useful to quickly free memory on servers running low, but
users should prefer tuning periodic garbage collection parameters to meet their
needs instead of relying on manually running `system gc`.
## Usage
```plaintext
nomad system gc [options]
```
If ACLs are enabled, this option requires a management token.
## Examples
Running the system gc command does not output unless an error occurs:
```shell-session
$ nomad system gc
```
## General options
@include 'general_options_no_namespace.mdx'