Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
Description
As the SQL cache store does not support expiration as documented but the configuration allow to set it the behavior is confusing after restart as the meta data is not stored.
Run the cache from scratch will add all entries with expiration meta-data, the entries are correctly removed from memory and persistence at expiration time.
But if the server is restarted and the cache is reloaded from the persistence the expiration meta information is lost, as result the entries are immoral until the next update.
The expectation is that the cache configuration for SQLstore is rejected if expiration is enabled to prevent from this behavior. This is similar to the segmentation=true.