Microservice running Rqueue is greedy in disk space?! about rqueue HOT 6 CLOSED

I have plan for it, but my project is still in beta and not fully stable. I will do this, when I add more content to the website. :)

from rqueue.

Once again thanks for reporting issue in Rqueue.

I'm also not sure what's going on here, I would need one small help from you for this bug, please see what's on that docker image? Could it be case that you have enabled logging and that dump lot of log data, Rqueue as such should not log so much data but if you have enabled debug level than this could be the case. If you find log level is debug than please switch to Info, error, warning etc.

Please consider also running below command to see which dir has the highest storage.

You can run this command on the host machine if you have mounted the volumes otherwise run it inside container. This command will provide us the detail about the dir that's consuming most of the storage. As it would be the root, so please get top 50 or top 10 to see which dir has the highest storage volume.

sudo du -a / | sort -n -r | head -n 50

from rqueue.

Rqueue as such should not log so much data but if you have enabled debug level than this could be the case

logging.level.ROOT: INFO it's already info by default in production. As the server don't have anything else running that could log that much of data.

As it would be the root, so please get top 50 or top 10 to see which dir has the highest storage volume.

i did that, but didn't find any big files, as logs are not showing there. i have noticed that i have many console errors are showing due to a bug, i will fix it, and monitor the disk space again and let you know.

from rqueue.

Here's the another thread, it's finding is also about log file. So it's most likely log file only.
https://www.digitalocean.com/community/questions/cannot-find-what-is-filling-up-disk-space-dev-vda1-is-100-full

from rqueue.

I had the same idea also. from the moment i reduced the exceptions stack trace from the log, the disk storage became accepted.
since i'm updating the server concurrently, i can't confirm that the exceptions stack trace are the cause. also, i have reduced all unneeded logs.

for now, i will close the issue, If one day i saw something weird related to the MS used storage, i will let you know.

thanks for your time and your help. :)

from rqueue.

@chlegou I would love to add your organisation name in the Readme file, if you're ok with that. This will just let others know really someone is using Rqueue in production and their scale :)

https://github.com/sonus21/rqueue/#in-production

Thanks

from rqueue.