Monitor a Job

After submitting the job, users are directed to the job progress view page.

Job Scheduled

While the job is still in the queue, none of the allocated computational resources are utilized. The progress view page in this case appears as shown in the image below.

Users can remove the job from the queue before the run starts by clicking the

    Cancel reservation

button.

Job Running

After the job status is set to running, the progress view page is split into different panels, as depicted below.

From these panels, users can view various information about the running job. For instance, users can extend the job lifetime at any moment during the run by selecting a certain amount of hours from the Time allocation panel.

Users can also terminate the job before the time limit is reached by using the

    Stop application

button. Additionally, while the job is running, users can open a terminal interface within the app by clicking on

 Open terminal

Depending on the app type, users may also have the option to open a custom software graphical interface.

Important

UCloud performs accounting at regular intervals during the job lifetime. If users run out of credits before job completion, the jobs will be terminated.

If the job has been started with SSH enabled and/or public links, the SSH command and links are displayed under the SSH and Links tab in the top-right panel (see image above).

Monitoring job resource usage

The top-right panel of the job progress view displays widgets that show the job’s CPU, memory, network, and, if available on the node, GPU and GPU memory usage in real time. Depending on the application, additional widgets may also be available.

Note

If the Job report sample rate optional parameter has been set during job submission, the data points for the different usage graphs are stored in /work/job-report.csv which is also available after job completion from the job completion page.

Job Completed

Once the job is completed, the path to the job output folder, with the associated link, and the job results will be available on the progress view page:

The job output folder is also reachable in the Jobs directory.

In addition to the job output files, a number of files are generated

• stdout.txt: This file replicates the program's standard output. It can be helpful for debugging in the case of a failure run.

• JobParameters.json: This file contains a record of the parameter values used to submit the job. It is written in JSON format (see here for an example). The JSON configuration file is utilized to load all job options simultaneously.

• job-report.csv: This file contains resource usage data for the job. The file is only created if the Job report sample rate optional parameters was set or enabled globally.

• job-0.sh: This file contains the command which is used in the UCloud backend to start the job. The file is usually not directly relevant for users.

• Several hidden files such as .ucviz-data, .ucmetrics-stats, .script-template.j2 etc. These are usually not directly relevant for users.

From this page, users can modify the content of the job output folder (by uploading files or creating new folders) and/or perform various operations (such as renaming, downloading, deletion, etc.) on the job output files. This can be done by clicking on a file and selecting the desired operation.

Finally, users can rerun the application with the same parameter values by clicking on the

Run application again

button.