Session ownership data is never removed from Redis
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- redis, typescript
Research direction
Inspect the transport-data cleanup path and the Redis key session:${sessionId}:owner. Reproduce the repeated create-and-finish session sequence, then verify that ownership data is removed when a session finishes or expires after a defined period, without continuing to accumulate in Redis.
Written by the indexing model from the issue text.
Description
Describe the bug
Session ownership data is being stored in redis and don't have TTL or are removed
To Reproduce
Steps to reproduce the behavior:
- Create Session
- Finish Session
- Repeat a big number of times
Expected behavior
Session ownership should be cleaned from Redis when session is finished or after a prudential amount of time
Logs
Additional context
Service is storing session ownership info in redis using session:${sessionId}:owner but this data is not removed when cleaning up the transport data. This can cause a memory leak over time if no clean up mechanism is implemented.
- Dominant language
- TypeScript
- Stars
- 80
- Forks
- 39
- Avg merge
- 43m
- Merged PRs (30d)
- 1
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.
More from modelcontextprotocol/example-remote-server
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
-
Missing License file Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
modelcontextprotocol/example-remote-server#11 · 1 reaction ·
All issues in modelcontextprotocol/example-remote-server
Similar issues
-
clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
supermomonga/zcode-acp#24 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
growthbook/growthbook#7100 ·
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100