Implement replicated session touch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 668
- Forks
- 135
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 7
Description
Currently, a user session is expired after a few hours since login regardless of your activity. The session expiration time should be extended (i.e. the session has to be touched) when a user sends any request.
We cannot touch a session on every single access because it updates the session storage and such event should be propagated to all replicas. We do not want to flood our replication queue. i.e. We need some batching like sending a group of session IDs every 10 minutes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how user requests access session storage and how session updates enter the replication queue. Define the batching interval and propagation behavior for recently accessed session IDs, then verify that active sessions receive an extended expiration without flooding replicas.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100