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

Feature: Ensure native velero datamover has parameterized concurrency #242

Open
weshayutin opened this issue Jun 14, 2023 · 0 comments
Open

Feature: Ensure native velero datamover has parameterized concurrency #242

weshayutin opened this issue Jun 14, 2023 · 0 comments

Comments

@weshayutin
Copy link
Collaborator

weshayutin commented Jun 14, 2023 •
edited
Loading

https://github.com/vmware-tanzu/velero/blob/78025a09b6107822a6f7c430c1d538a39c651ee7/pkg/controller/data_upload_controller.go#LL86C3-L86C3

At this time in velero 1.12 cycle there isn't bandwidth to test and fix anything greater than 1 xfer per node.
After release...

  • [] propose small design for parameter name in spec
  • [] update value to 2 and fix bugs
  • [] merge in main
  • [] backport to velero 1.12
@weshayutin weshayutin changed the title Ensure native velero datamover has parameterized concurrency Feature: Ensure native velero datamover has parameterized concurrency Jun 14, 2023
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
OADP-1.3
Status: No status
Milestone
No milestone
Development

No branches or pull requests
1 participant
@weshayutin