Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-1179 Integrity checking in Pegasus
  3. PM-1254

handling of checkpoint files for integrity checking

    XMLWordPrintable

    Details

    • Type: Sub-task
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: master
    • Fix Version/s: master, 4.9.0
    • Component/s: pegasus-plan
    • Labels:
      None

      Description

      Pegasus has a notion of a checkpoint file that user can designate for their jobs.

       <job id="j1" namespace="pegasus" name="checkpoint" version="4.0">
            <argument>-o <file name="f.b1"/> -o <file name="f.b2"/></argument>
            <uses name="f.a" link="input"/>
            <uses name="f.b1" link="output" transfer="true" register="true"/>
            <uses name="f.b2" link="output" transfer="true" register="true"/>
            <uses name="test.checkpoint" link="checkpoint" transfer="true" register="true"/>
         </job>


      the semantics of this file, is that the updated version of the checkpoint file is available whenever a job is retried with it's last copy.

      When the application code succeeds the application code is expected to delete the checkpoint file.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: