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

DataMover - distribute datadownload evenly across nodes if possible #8242

Open
Lyndon-Li opened this issue Sep 24, 2024 · 2 comments
Open

DataMover - distribute datadownload evenly across nodes if possible #8242

Lyndon-Li opened this issue Sep 24, 2024 · 2 comments

Comments

@Lyndon-Li
Copy link
Contributor

As a part of #6734, related to #8044 and #8186. At present, Velero Generic Restore doesn't consider the distribution across nodes because of #8044, once we enhance it, the restore activities should be distributed evenly across nodes whenever possible.

@reasonerjt
Copy link
Contributor

reasonerjt commented Oct 12, 2024

I'm not sure if this is better than letting k8s scheduler decide the placement of restore-pod, therefore we may introduce a configuration set for restore-pod in "node-agent-configuration"

@reasonerjt
Copy link
Contributor

If #8044 is fixed, i.e. we introduce a flag to allow restore pod to ignore the "WaitForFirstConsumer" attribute in storage class, we can run datadownload in parallel and allow better distribution of restore pods.

@reasonerjt reasonerjt added this to the v1.16 milestone Oct 31, 2024
@weshayutin weshayutin added this to OADP Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants