Ganga job states and their transitions

The job.status property, which holds the state information, is a string and it is the responsability of the backend handlers to comply with this definition (it is not otherwise enforced). Each submission backend should provide a mapping from internal backend states to one of the following Ganga states ( transitions in the diagram below).

  • running : application is being executed
  • completed : application finished correctly (for example, executable exit code is 0) and the output sandbox have been correctly retrieved
  • failed : application failed, or backend error (such as unable to retrieve the output sandbox)

This mapping is done in backend.updateMonitoringInformation() method.

For master jobs, the status is derived from the status of subjobs, according to the algorithm defined by job.updateMasterJobStatus(). This method should be used by backend plugins if they override backend.master_updateMonitoringInformation() method.

All other states are assigned by Ganga automatically.

user-states.gif

-- JakubMoscicki - 18-Feb-2011

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2011-02-18 - JakubMoscicki
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    ArdaGrid All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback