Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Tech Request]: proxy migrate sessions #13890

Closed
2 tasks done
volgariver6 opened this issue Dec 28, 2023 · 1 comment
Closed
2 tasks done

[Tech Request]: proxy migrate sessions #13890

volgariver6 opened this issue Dec 28, 2023 · 1 comment
Assignees
@volgariver6
Labels
kind/tech-request New feature or request priority/p0 Critical feature that should be implemented in this version
Milestone
1.2.1

Comments

@volgariver6
Copy link
Contributor

Is there an existing issue for the same tech request?

  • I have checked the existing issues.

Does this tech request not affect user experience?

  • This tech request doesn't affect user experience.

What would you like to be added ?

Proxy transfer connections between CN servers when rebalance or scale-in is needed.

The following info has been migrated currently:

- DB info
- session var
- prepare stmt(mysql client only, not jdbc)

Other info need to be migated with high priority:

- prepare stmt (for jdbc)
- last query ID
- sequence ID in mysql protocol
- create sequence
- query result
- global variables(consistency consideration)

And those with low priority:

- stats cache
- plan cache
- temp table

Why is this needed ?

No response

Additional information

No response
@volgariver6 volgariver6 added the kind/tech-request New feature or request label Dec 28, 2023
@volgariver6 volgariver6 self-assigned this Dec 28, 2023
@volgariver6 volgariver6 mentioned this issue Dec 28, 2023
Closed
@volgariver6 volgariver6 added this to the 1.2.0 milestone Dec 28, 2023
@sukki37 sukki37 added the priority/p0 Critical feature that should be implemented in this version label Jan 5, 2024
@sukki37 sukki37 modified the milestones: 1.2.0, 1.2.1 May 28, 2024
@volgariver6
Copy link
Contributor Author

close it as it is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@volgariver6 volgariver6

Labels
kind/tech-request New feature or request priority/p0 Critical feature that should be implemented in this version
Projects
None yet
Milestone
1.2.1
Development

No branches or pull requests
2 participants
@volgariver6 @sukki37