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

Pegasus does not parse -Ddagman.X properties in the argument string for the DAX jobs.

XMLWordPrintable

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Minor Minor
    • 3.0.3, 3.1
    • Affects Version/s: master, 3.0.2
    • Component/s: Pegasus Planner
    • None

      While parsing arguments for a DAX job, pegasus does not parse -Dpropertyname=value option correctly.
      Since 3.0 users can addition to specifying pegasus properties, can specify profiles as properties for example -Ddagman.datafind.maxjobs

      <dax id="ID000026" file="inspiral_hipe_bnsloginj_cat3_veto.BNSLOGINJ_CAT_3_VETO.dax">
      <argument>-Dpegasus.dir.storage=bnsloginj -Ddagman.datafind.maxjobs=10 -Ddagman.sire.maxjobs=20 -Ddagman.coire.maxjobs=20 -Ddagman.thinca.maxjobs=20 -Ddagman.trigbank.maxjobs=20 --dir bnsloginj --nocleanup --cluster horizontal -vvvvvv --force</argument>
      </dax>

      When pegasus plans this DAX job the dagman properties disappear from the pre script invocation

            Assignee:
            vahi Karan Vahi
            Reporter:
            vahi Karan Vahi
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: