Status Definitions#
CONVERGE Horizon displays a status for every cloud resource that users create. The possible status values for each type of resource are described below.
File System Status#
A file system can have any of the statuses listed below.
- Pending:
CONVERGE Horizon is requesting a storage device and a virtual machine (VM) from the cloud provider.
- Provisioning:
CONVERGE Horizon is attaching the storage device to the VM and setting up the file system.
- Online:
The file system is available for use.
- Hibernating:
The file system is hibernating.
- Deleting:
CONVERGE Horizon is deleting the file system.
- Deleted:
The file system has been deleted and the hardware has been released.
Job Status#
A job can have any of the statuses listed below.
- Batched:
The job has been added to a batch. The job will remain at this status until a user starts the batch.
- Pending:
The job has been added to the queue. CONVERGE Horizon is requesting hardware from the cloud provider.
- Provisioning:
CONVERGE Horizon is provisioning nodes allocated by the cloud provider. This includes software installation and configuration.
- Running:
The simulation is running on the provisioned nodes.
- Interactive:
The job is running in Interactive mode.
- Stopping:
CONVERGE Horizon is stopping the job. If the job was run from a space, this is when output files are uploaded to the space. To avoid unnecessary hardware charges, the cluster may be resized to remove excess nodes that are not utilized during the upload process.
- Stopped:
The job has stopped. This either means that CONVERGE ran to completion or that the simulation was stopped with a STOP file.
- Failed:
The job failed.
Job Outcomes#
CONVERGE Horizon displays an outcome for all stopped and failed jobs. Explanations of possible job outcomes are listed below. For help investigating issues you cannot resolve on your own, request support from our team.
- Completed:
CONVERGE ran to completion.
- Application crashed:
CONVERGE did not run successfully, most likely because of case setup issues. Check the horizon.log file for runtime errors. If you see errors in the log file, adjust your case setup as directed and create a new job.
- Application stuck:
CONVERGE Horizon stopped the job because it was stuck and the Time Limits > Stop if stuck option was enabled.
- Maximum queue time reached:
The cloud provider was unable to allocate the requested node(s) within the specified maximum queue time.
- Time limit reached:
The job was stopped because the runtime reached the specified time limit.
- Stopped by a user:
A user stopped the job. The output files were retained unless the user chose to discard them.
- Stopped by CONVERGE Horizon:
The CONVERGE Horizon team stopped the job.
- Batch stopped:
A user stopped the batch to which the job belongs. The output files were retained unless the user chose to discard them.
- Out of disk space:
CONVERGE Horizon stopped the job because the size of the cluster’s scratch storage exceeded the allowed limit. The size of scratch storage is dynamically adjusted to make space for the output files and cannot exceed 10 TB. If a simulation generates enough output data to exceed this limit, CONVERGE Horizon will stop the job.
- Hardware failed:
CONVERGE Horizon stopped the job because the job’s hardware failed or stopped responding.
- Hardware reclaimed:
The cloud provider reclaimed the spot hardware on which the job was running. The simulation ended immediately, and the output files were retained. If Hardware > Requeue if reclaimed was enabled, CONVERGE Horizon created a new job with the same settings.
- Storage unavailable:
The file system or space containing the input files was no longer available when CONVERGE Horizon was setting up the job.
- Billing limit reached:
CONVERGE Horizon stopped the job because your organization’s balance was equal to or less than a billing limit configured by your organization owner.
- Hardware not offered:
The selected node type was no longer offered in the data center when the job was ready to start.
Batch Status#
A batch can have any of the statuses listed below.
- Pending:
The batch has been created and you can add jobs to it. None of the jobs will run until you start the batch.
- Running:
The batch has started and jobs are being run according to the batch configuration. You cannot add jobs to a running batch.
- Stopping:
CONVERGE Horizon is stopping the batch. Any jobs in the batch that have not already stopped or failed are being stopped.
- Stopped:
All jobs in the batch have stopped or failed.
Workstation Status#
A workstation can have any of the statuses listed below.
- Pending:
CONVERGE Horizon is requesting a workstation node from the cloud provider.
- Provisioning:
CONVERGE Horizon is provisioning the node allocated by the cloud provider. This includes software installation and configuration.
- Online:
The workstation is ready for use. You can connect to the workstation to run pre- and post-processing applications.
- Deleting:
CONVERGE Horizon is deleting the workstation.
- Deleted:
The workstation has been deleted, either because the time limit was reached or because a user deleted it. The workstation node has been released.