Skip to content

Quick upgrade by starting another newly instance #188

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
Closed
zuston opened this issue Mar 28, 2025 · 1 comment
Closed

Quick upgrade by starting another newly instance #188

zuston opened this issue Mar 28, 2025 · 1 comment

Comments

@zuston
Copy link
Owner

zuston commented Mar 28, 2025

To speed up upgrading, we'd better to start a new instance to upgrade, and make another instance decommission. To ensure this feature, we should use another port like grpc + urpc or http service.
And the disk detection file name should involve the service ID to ensure unique.
@zuston zuston changed the title Start a new instance to upgrade Quick upgrade by starting another newly instance Apr 2, 2025
@zuston
Copy link
Owner Author

zuston commented Apr 2, 2025

  1. feat: Bound server_id into log parent folder #193
  2. feat: Bound shuffle_server_id into disk detection file name to ensure unique #189
  3. feat: Introducing option to control disk pre launch purge #192

@zuston zuston closed this as completed Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@zuston