← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1690756] [NEW] cache 'backend' argument description is ambiguous

 

Public bug reported:

The oslo.cache backend argument description currently states:

"Dogpile.cache backend module. It is recommended that Memcache or Redis
(dogpile.cache.redis) be used in production deployments. For eventlet-
based or highly threaded servers, Memcache with pooling
(oslo_cache.memcache_pool) is recommended. For low thread servers,
dogpile.cache.memcached is recommended. Test environments with a single
instance of the server can use the dogpile.cache.memory backend."

So the dogpile.cache.memcached/dogpile.cache.redis backends should be
used for production deployments, but the dogpile cache is recommended
for low thread servers and the oslo_cache.memcache_pool should be used
for high thread servers. I don't understand what the actual
recommendation is here.

For a production deployment of a service using uwsgi and a web server, what is the recommendation?
For a production deployment of a service using uwsgi and no web server, what is the recommendation?
For a production deployment of a service using eventlet, what is the recommendation?

Using keystone as an example, the example config file has the same
content which does not really help to clarify anything:

https://github.com/openstack/keystone/blob/b7bd6e301964d393ac6835111a08bbf15ba73bc0/etc/keystone.conf.sample#L514-L520

** Affects: keystone
     Importance: Undecided
         Status: New

** Affects: oslo.cache
     Importance: Undecided
         Status: New

** Also affects: keystone
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1690756

Title:
  cache 'backend' argument description is ambiguous

Status in OpenStack Identity (keystone):
  New
Status in oslo.cache:
  New

Bug description:
  The oslo.cache backend argument description currently states:

  "Dogpile.cache backend module. It is recommended that Memcache or
  Redis (dogpile.cache.redis) be used in production deployments. For
  eventlet-based or highly threaded servers, Memcache with pooling
  (oslo_cache.memcache_pool) is recommended. For low thread servers,
  dogpile.cache.memcached is recommended. Test environments with a
  single instance of the server can use the dogpile.cache.memory
  backend."

  So the dogpile.cache.memcached/dogpile.cache.redis backends should be
  used for production deployments, but the dogpile cache is recommended
  for low thread servers and the oslo_cache.memcache_pool should be used
  for high thread servers. I don't understand what the actual
  recommendation is here.

  For a production deployment of a service using uwsgi and a web server, what is the recommendation?
  For a production deployment of a service using uwsgi and no web server, what is the recommendation?
  For a production deployment of a service using eventlet, what is the recommendation?

  Using keystone as an example, the example config file has the same
  content which does not really help to clarify anything:

  https://github.com/openstack/keystone/blob/b7bd6e301964d393ac6835111a08bbf15ba73bc0/etc/keystone.conf.sample#L514-L520

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1690756/+subscriptions


Follow ups