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

Design: ACM performance use case - restore 30k secrets #1044

Closed
6 tasks
weshayutin opened this issue May 31, 2023 · 6 comments
Closed
6 tasks

Design: ACM performance use case - restore 30k secrets #1044

weshayutin opened this issue May 31, 2023 · 6 comments
Assignees
@sseago
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@weshayutin
Copy link
Contributor

weshayutin commented May 31, 2023 •
edited
Loading

See: https://issues.redhat.com/browse/OADP-1167 for context

  • Backup all ACM resources, time to backup about 4min ( 28202 resources )

  • Run a restore on the same hub, restoring the above backup ( so all resources already exist, they are just updated and tagged with the restore label) : 1h12min - this time is too high.. especially since this restore is executed on a passive hub and would be re-run as soon as new backups are available

  • Investigate where the restore issue may be coming from

  • Demo root cause to team

  • Propose solutions

  • Draft design for upstream Velero / OADP where applicable

  • Start implementation

  • Tests?
@weshayutin weshayutin moved this to New / Design in OADP-1.3 Jun 13, 2023
@weshayutin weshayutin moved this from New / Design to Todo in OADP-1.3 Jun 13, 2023
@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 19, 2023
@mateusoliveira43
Copy link
Contributor

Not stale, right? Scott already opened PR upstream vmware-tanzu/velero#6723

@weshayutin
Copy link
Contributor Author

@mateusoliveira43 correct

@weshayutin weshayutin moved this from Todo to Ready for Review in OADP-1.3 Sep 20, 2023
@kaovilai kaovilai added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 27, 2023
@mateusoliveira43
Copy link
Contributor

@sseago is this issue completed?

@shubham-pampattiwar
Copy link
Member

yeah fixed via vmware-tanzu/velero#6723

@kaovilai
Copy link
Member

kaovilai commented Dec 6, 2023

Jira has cloesd, so has the upstream issue.
vmware-tanzu/velero#6723

@kaovilai kaovilai closed this as completed Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sseago sseago

Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@weshayutin @sseago @openshift-bot @kaovilai @shubham-pampattiwar @mateusoliveira43