Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-645 Data mover performance on restore blocks restore process
  3. OADP-837

[IBM QE-Z] Verify Bug OADP-645 - Data mover performance on restore blocks restore process

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Set a Value
    • 0
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown

      Description of problem:

      As of right now, a velero restore currently blocks awaiting for the data mover action to complete before processing all of the plugins. We want to update the code to kick off all of the data mover processes asynchronously while allowing Velero to process the rest of its resources. Then Velero should wait for the data movers to complete before marking the restore as completed.

      Version-Release number of selected component (if applicable):

      1.1.0

      How reproducible:

      100%

      Steps to Reproduce:
      1. Run a restore with data mover enabled

      Actual results:

      Observe the logs of the velero pods and see that velero blocks waiting for a DM process to complete rather than processing all of its resources before waiting for it to complete.

      Expected results:

      Data mover process should be asynchronous

              mayaanilson Maya Anilson (Inactive)
              mperetz@redhat.com Maya Peretz
              Maya Anilson Maya Anilson (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: