Memcache not in use

Bug #1830981 reported by Giuseppe Petralia on 2019-05-29
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Designate Charm

Bug Description

charm-designate: revision 29 (Release 19.04)
openstack version: cloud:xenial-queens

In a Bootstack customer environment, designate is burning mysql constantly
holding 600+ processes from processlist.

We found that designate is not using memcache as cache backend,
however installed and configured.

In designate.conf we have

cache_driver = sqlalchemy

Instead of

cache_driver = memcache

Designate sample config for queens:

Changed in charm-designate:
status: New → Triaged
Alex Kavanagh (ajkavanagh) wrote :


It's true that the default of sqlalchemy is set in the designate.conf template for the charm. The memcache is currently used for coordination between designate instances, rather than as a caching service for the pool. There look to be quite a few memcached configuration options in the designate service, so it will need to be carefully thought through about how to add this feature.

Changed in charm-designate:
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers