Transfer grouping when some transfers need to be local and others remote

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major
    • master, 4.5.0
    • Affects Version/s: master
    • Component/s: Pegasus Planner
    • None

      We had this issue in SNS. I have several input files for the workflow that have file:// URLs with pool=local, and I have several others with file:// URLs with pool=hopper. For some reason that I don't understand, pegasus groups these transfers together and runs them in universe=local.

            Assignee:
            Karan Vahi
            Reporter:
            Gideon Juve
            Archiver:
            Rajiv Mayani

              Created:
              Updated:
              Resolved:
              Archived: