Community Edition doesn't support caching, but it still crashes if there's no Memcached/Redis server

Seafile Server
,
1

I’ve installed Seafile in a Kubernetes cluster. We’re using seafileltd/seafile-mc:12.0.6 image. And everything was fine until I’ve tried to issue API calls to Seafile:

“Sorry, but the requested page is unavailable due to a server hiccup.”

And after I’ve double-checked seahub.log, I’ve found that it’s requiring Memcached or Redis:

pylibmc.HostLookupError: error 2 from memcached_get(:1:autofilled): (0x480da70) getaddrinfo() or getnameinfo() HOSTNAME LOOKUP FAILURE, host: memcached:11211 → ./src/libmemcached/get.cc:233
2025-02-20 11:25:25,590 [ERROR] django.pylibmc:167 set_many MemcachedError: error 47 from memcached_set_multi: (0x480da70) SERVER HAS FAILED AND IS DISABLED UNTIL TIMED RETRY, host: m

But, why is this happening if docs states that caching is a professional edition feature?

image
image1100×560 65.9 KB

Is Memcached or Redis really required in Community Edition?

2

This section means that seaf-server component in Seafile Pro Edition uses memory caches in various cases to improve performance. (seaf-server component in community edition does not use cache)

Community edition in general need Memcached or Redis.