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

Unintuitive job names when using label-based clustering

XMLWordPrintable

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

      When I use label based clustering I often put different transformations into the same cluster. When pegasus plans these jobs it seems to randomly pick one of the transformations to use as the job name. For example, if I put xforms ns::foo and ns::bar in the same cluster, the job name might come out merge_ns-foo-_ID1 or it might come out merge_ns-bar-_ID1.

            Assignee:
            gideon Gideon Juve (Inactive)
            Reporter:
            gideon Gideon Juve (Inactive)
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: