On this page
Triggers the garbage collector on the source aggregator and propagates to all the leaves.
Garbage collection is a process where unneeded versioned nodes for multi-version concurrency are eliminated.
The garbage collection process automatically runs in the background, so it's normally not necessary to execute
TRIGGER GC [FLUSH].
TRIGGER GC [FLUSH] might be appropriate.
TRIGGER GC [FLUSH]
FLUSH: Releases all unused memory back to the operating system.
The garbage collector runs automatically.
You may still need to manually trigger the GC in the following scenarios:
If you need to free up the cached memory, use the
(SingleStoreDB only caches memory when it is available and not under any duress. Hence, this practice may turn out to be counter-productive because the caches will refill themselves over time as queries run. )
If one of the partitions is using more memory (while bulk-loading/deleting data or recovering from a restart) and you are forced to wait until the garbage collection completes.
This command can be run on any aggregator.
Only users with
SUPERprivileges can run this command.
Refer to the Permission Matrix for the required permission.
TRIGGER GC FLUSH;
Last modified: March 23, 2023