58b06c40d2
Current implementation of expiration time relies on the generation time stored in actual cache data, thus expired cache records are not removed from backends automatically. Add the new option to additionally set the expiration time supported by the cache backend, so that operators can limit amount of spaces (especially memory spaces) used for cache data. Closes-Bug: #1578401 Change-Id: If61871f030560079482ecbbefeb940d8d3c18968
8 lines
311 B
YAML
8 lines
311 B
YAML
---
|
|
features:
|
|
- |
|
|
The new ``[cache] enable_backend_expiration`` option has been added. When
|
|
this option is set to ``True``, all cache records are added to the cache
|
|
backend in use with expiration time, so that expired records are
|
|
automatically purged by the reclaiming feature in the backend.
|