Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-624

Properties propogation to sub workflows

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: master, 4.0.1
    • Fix Version/s: master, 4.0.1
    • Component/s: Pegasus Planner
    • Labels:
      None

      Description

      For an hierarchal workflow of the following structure
        uber-dax
         |--dax-group
            |--dax.0
            |--dax.1
            |--dax.2

      lets say we want uber-dax and dax-group wf's to be executed in shared filesystem setup , and dax.0 , dax.1 to be executed in the condorio mode

      The dax.1 when planned by pegasus will see pegasus.execute.*.filesystem.local set to false , as that is inherited from dax-group

      Because of this , when planner on encountered the pegasus.data.configuration property as condorio tries to pegasus.execute.*.filesystem.local to true , it does not saying it has been already set in properties

      012.06.22 17:09:16.941 EDT: [WARNING] Property Key pegasus.execute.*.filesystem.local already set to false. Will not be set to - true

      The current logic says that
      If this is already set in the properties, don't override



      One way to get around this is to have pegasus.execute.*.filesystem.local set explicitly in the DAX

      <dax id='scan-flowgid0' file='scan-flow.0.dax' >
            <argument>-Dpegasus.execute.*.filesystem.local=true -Dpegasus.data.configuration=condorio --staging-site=local --verbose --verbose --verbose --force --sites condorpool</argument>
         </dax>

        Attachments

          Activity

            People

            • Assignee:
              vahi Karan Vahi
              Reporter:
              vahi Karan Vahi
            • Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: