As the long-running scheduler and execution environment process a grid compute-intensive job, the job state updates in the long-running scheduler database.
The following table lists the possible states that a compute-intensive job can have and the events that trigger state transitions. You can view the current state of a compute-intensive job in the administrative console job management panels, or retrieve the state using the command line, enterprise bean, or Web service interfaces to the long-running scheduler.
Start state | Client command | LREE action | Special condition | End state |
---|---|---|---|---|
pending submit | submit | none | job is submitted when start time expires | submitted |
non-existent | submit | (non-applicable) | (non-applicable) | submitted |
submitted | (non-applicable) | dispatch | (non-applicable) | executing |
submitted | cancel | (non-applicable) | (non-applicable) | cancelled |
executing | cancel | (non-applicable) | (non-applicable) | cancel_pending |
executing | (non-applicable) | caught application error++ | (non-applicable) | execution_failed |
executing | (non-applicable) | (non-applicable) | Infrastructure problem+++ | execution_failed |
executing | (non-applicable) | job completed | (non-applicable) | ended |
cancel_pending | (non-applicable) | job cancelled | (non-applicable) | cancelled |
cancel_pending | (non-applicable) | (non-applicable) | Infrastructure problem+++ | execution_failed |
cancelled | purge | (non-applicable) | (non-applicable) | non-existent |
execution_failed | purge | (non-applicable) | (non-applicable) | non-existent |
ended | purge | (non-applicable) | (non-applicable) | non-existent |
++ Application error |
The compute intensive application threw an exception during execution that was caught by the long-running execution environment. |
+++ Infrastructure problem |
An unprecedented error has occurred. For example, a power outage. |
+Infrastructure problem |
An unprecedented error has occurred. For example, a power outage. |