-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.0, 4.0.8
-
MOODLE_400_STABLE
Found while testingĀ MDL-68608
I don't think we want to change the semantics of the cache API so that session caches are tightly bound to sessions - we want to actively decouple these even more to enable readonly sessions.
So I think the correct solution here is to add support for event based invalidation in a readonly session, which requires touch points in the session store to be aware of write_close and also in the cache api to correctly handle when a purge did not succeed and to try again later.
Reproduction steps:
- add MDL-69977-session-cache-write-close.php to a site
- load this page a couple times
- confirm the counter stored in the session before it is closed is incrementing
- confirm that the counter store in MUC after the session is closed is not incrementing (and it should be changing, or logging an error)
- has a non-specific relationship to
-
MDL-75813 Session cache store breaks cache api when session is closed or readonly - deprecate cachestore_session
- Open
-
MDL-79161 Add support for redis key eviction polices by caching using SET+EXPIRE instead of HSET
- Open
-
MDL-68608 Improve the readonly session debugging message
- Closed
- will be (partly) resolved by
-
MDL-73317 Detect and add debugging for when the session is changed after it has been closed
- Closed