Identity supports a caching layer that is above the configurable subsystems,
such as token or assignment. The majority of the caching configuration options
are set in the [cache]
section. However, each section that has the
capability to be cached usually has a caching
option that will toggle
caching for that specific section. By default, caching is globally disabled.
Options are as follows:
Configuration option = Default value | Description |
---|---|
[memcache] | |
dead_retry = 300 |
(Integer) Number of seconds memcached server is considered dead before it is tried again. This is used by the key value store system (e.g. token pooled memcached persistence backend). |
pool_connection_get_timeout = 10 |
(Integer) Number of seconds that an operation will wait to get a memcache client connection. This is used by the key value store system (e.g. token pooled memcached persistence backend). |
pool_maxsize = 10 |
(Integer) Max total number of open connections to every memcached server. This is used by the key value store system (e.g. token pooled memcached persistence backend). |
pool_unused_timeout = 60 |
(Integer) Number of seconds a connection to memcached is held unused in the pool before it is closed. This is used by the key value store system (e.g. token pooled memcached persistence backend). |
Current functional back ends are:
dogpile.cache.memcached
python-memcached
library.dogpile.cache.pylibmc
pylibmc
library.dogpile.cache.bmemcached
python-binary-memcached
library.dogpile.cache.redis
dogpile.cache.dbm
dogpile.cache.memory
dogpile.cache.mongo
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.