From 72918c8d6a399cd8eb2e98119b6b4e1e663342cd Mon Sep 17 00:00:00 2001
From: zkldi <20380519+zkldi@users.noreply.github.com>
Date: Sun, 24 Jul 2022 16:14:46 +0100
Subject: [PATCH] EMERG: Clean up score import jobs after they are ran.

WHY IS THIS NOT THE DEFAULT???

We've been shredding our servers disk and generally getting into
trouble by having redis infinitely balloon up score imports
and then writing them to disk for backup.
we were writing upwards of 200Mbit/s.

Goddamnit bull.
---
 server/src/lib/score-import/worker/queue.ts | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/server/src/lib/score-import/worker/queue.ts b/server/src/lib/score-import/worker/queue.ts
index fa2878e49..642bfdc35 100644
--- a/server/src/lib/score-import/worker/queue.ts
+++ b/server/src/lib/score-import/worker/queue.ts
@@ -3,6 +3,10 @@ import { Environment, TachiConfig } from "lib/setup/config";
 
 const ScoreImportQueue = new Queue(`${TachiConfig.NAME} Score Import Queue`, {
 	connection: { host: Environment.redisUrl, port: 6379 },
+	defaultJobOptions: {
+		removeOnComplete: true,
+		removeOnFail: 10, // keep the last 10 failed jobs, but start pruning beyond that.
+	}
 });
 
 export default ScoreImportQueue;