Agreed. I can’t imagine how there could be 16GB of redis. If you move to a new server, what’s in redis (typically) gets left behind, so one thing to do would be to just delete it and rebuild.
You can see what this says:
cd /var/discourse
./launcher enter app
redis-cli
info memory
exit
exit
exit
Also, for interest, at the bottom of your forum’s sidekiq status page (forum.url/sidekiq) there’s a summary of Redis memory usage, including peak usage. (Also, uptime - might be interesting if uptime is very short, because maybe redis is crashing and restarting and leaving some disk clutter.)
(However, that’s memory usage, and the problem here seems to be disk usage.)
Is this a standard install? Does it have a history of being migrated from another machine? A quick search indicates that some kind of permissions problem, or other reason for redis to fail while saving/renaming, could be the cause.
I think that they get left behind if redis shuts down before it can write it out. (But had no memory of writing that, so maybe I have it left in a temp file solfege/somewhere)
There’s certainly something wrong. It’s this an underpowered machine? It’s it running a bunch of AI stuff? (I don’t think so, but those are my best guesses)
If safe to delete them, which solves the immediate disk space issue.