What is the difference between HVR job states, PENDING & UNSUSPEND in the Scheduler?
Local Data Processing
The HVR Scheduler schedules jobs. Each job performs a certain task. At any moment a job is in a certain state. For instance, when a job is waiting to be run, it is in state PENDING; when a job is running, it is in state RUNNING.
Jobs can be either acyclic or cyclic.
Acyclic jobs will only run once, whereas cyclic jobs will rerun repeatedly.
When an acyclic job runs, it goes from state PENDING to RUNNING and then disappears.
Cyclic jobs when it runs, it goes from state PENDING to RUNNING and then back to state PENDING. In this state it waits to receive a signal (trigger) in order to run again.
If for some reason a job fails to run successfully the scheduler will change its state first to ALERTING, then RETRY and will eventually run again. If a job stays in state RUNNING for too long it may be marked with state HANGING; if it finishes successfully it will just become PENDING.
- START mean you want to start job immediately.
- UNSUSPEND means you allow the scheduler to kick it off at the scheduled time. You can also "Unsuspend" integrate to get it to a job that is scheduled to a PENDING state.
- For a normal refresh and compare if you have not configured a schedule then Unsuspend will do nothing. For a normal capture or integrate job that has a schedule defined unsuspend will simply result in it getting started.