Open akhil1508 opened 1 month ago
@the-djmaze If you can give some pointers/guidance, would be happy to develop to fix this
I don't know how space your cache is using. But maybe use memcache?
And disable cache could also be an option if imap is fast.
A periodic rm -dfr /cache
might be faster.
@the-djmaze
I don't know how space your cache is using.
It's not a lot of space but it's a lot of folders.. and rm
is a slow operation on cephfs with thousands of folders with many subfolders each
But maybe use memcache?
This is what I don't understand. I already use APCU as the cache, why is the app still using files to cache?
When creating the \MailSo\Cache\DriverInterface
fails, it will use the File driver.
That's why you have a lot of cache files.
You must check your cache driver settings.
You must check your cache driver settings.
@the-djmaze I am checking this.
In the meantime until I can debug it could you tell me if it is safe to do:
occ app:disable snappymail
mv cache some-other-location/cache
occ app:update snappymail
occ app:enable snappymail
I've actually had to do the mv
step in during update before as it was extremely slow and users were complaining about downtime.
Yes, that is safe enough.
Describe the bug
occ app:update snappymail
, there is a downtime of at least 20 minutes (sometimes much more, up to 3h)apcu
files
so it was doing anrmdir
on all the files when the app was updating; it used to take upwards of an hour to update snappymail thenunlink appdata_snappymail/_data_/_default_/cache/__/ab/cd/{username_domain}/ef/gh/abcdefghigk
To Reproduce Steps to reproduce the behavior:
On a big nextcloud instance
occ app:disable snappymail
occ app:update snappymail
occ app:enable snappymail
Expected behavior