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.

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

Enable enable_real_chunk_locations before update to 24.2 #396

Closed
l0kix2 opened this issue Nov 21, 2024 · 0 comments · Fixed by #412
Closed

Enable enable_real_chunk_locations before update to 24.2 #396

l0kix2 opened this issue Nov 21, 2024 · 0 comments · Fixed by #412

Comments

@l0kix2
Copy link
Collaborator

l0kix2 commented Nov 21, 2024

Prior to datanodes update we should add a k8s job, that would set //sys/@config/node_tracker/enable_real_chunk_locations=%true if image version is in a range 23.2 — 24.1. It is required to enable update to 24.2 in the future.

After that we will ask users to update ytop to the version with this fix and run update (full or data nodes only) @ 23.2 or 24.1 version.

N.B. Such update should be done with re-creating all ytsaurus nodes pods, which is default behaviour for full update (which is triggered when master image is updated). Node restart wouldn't happen with updateSelector=MasterOnly, but we consider updateSelector experimental functionality for those who knows what they doing (for example they can restart nodes themselves to have less downtime).

Extra details:

  • job should run on both cluster create (Initialization state) and update (Updating state) before dnd pods are created/recreated
  • remote data nodes also should have the same workflow (though if they exist they will require separate update with new ytop version)
@l0kix2 l0kix2 changed the title Enable enable_real_chunk_locations with update to 24.2 Enable enable_real_chunk_locations before update to 24.2 Nov 21, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in yt-k8s-operator project Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant