Regarding the Redis session handler in https://tracker.moodle.org/browse/MDL-55602, I was wondering why the session data expires at the same rate as the locks?
If I set the lock timeout to 5 seconds, after 5 seconds of inactivity on Moodle the entire session will be expired and destroyed, whereas I would want the session data to stay there but just have the locks timeout after 5 seconds. I realise 5 seconds is a bad number, it just works well for demonstrating the issue.
It seems to have been specifically coded this way, with setex and expires calls against the session data key so am I just missing something?