https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16758

--- Comment #5 from Jacek Ablewicz <a...@biblos.pk.edu.pl> ---
(In reply to Jacek Ablewicz from comment #4)

> That should work fine IMO, without significant performance hit (as long as
> L2 is memcached).

But if L2 = Cache::Memory, this will be effectively just a null op.

This might happen e.g. if the caching system is not configured quite
consistently (due to MEMCACHED_* environment variables not exported by default
for system & maintenance scripts). I'm not sure if it's still an issue for
packaged debian installs or not (AFAIRC it was an issue at least in 3.22.*
about 4 months ago).

BTW, I'm wondering what is an order of starting koha-common && memcached in
debian packaged installs? If on server reboot indexer daemon gets started
before memcached is up and running, it will default to Cache::Memory as well,
even if the MEMCACHED_* variables are set up properly.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
Koha-bugs@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to