Parallel the session migration process
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 73
- Forks
- 41
- Avg merge
- 21h 3m
- Merged PRs (30d)
- 21
Description
Development Task
Currently, the process of session migration is serial:
- Query the session states
- Find a backend
- Connect to the backend and retry if it fails
- Read the initial handshake from the new backend
- Handshake with the new backend
- Set the session states into the new connection
- Disconnect the old connection
A long session migration may affect the query duration. We can do the 1st step while doing the 2nd, 3rd, and 4th steps. It may reduce the session migration duration.
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
No file or test is named. Start by locating the session migration entry point and tracing the seven listed steps, then identify where the first query can overlap with backend connection and handshake work. Done means the migration performs the proposed overlap and its duration or query impact can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100