Spring Redis Session - TTL gets reset back to original timeout when deleteSession attempt is made

I'm not sure if this is expected behaviour, but if my session timeout is 5 minutes the timeout on the hashed key is 10 minutes (an extra 5 minutes)

However, when I try to delete a key, the key remains and only the lastAccessedTime is left in there. However the ttl gets reset to 5 / 10 minutes again.

Is that expeced behaviour? Would seem strange when trying to invalidate a 6 hour long session, with 1 hour left for it to get reset back to 6 hours again?

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior.

Expected behavior
A clear and concise description of what you expected to happen.

Sample

A link to a GitHub repository with a minimal, reproducible sample.

Reports that include a sample will take priority over reports that do not.
At times, we may require a sample, so it is good to try and include a sample up front.

Start with the Spring Redis session implementation and the deleteSession path described in the report. Reproduce the hashed-key TTL reset after deletion, then determine the expected expiration behavior and add a regression test showing that invalidation does not incorrectly restore the original timeout.