JobHistoryView
Lists each queued instance of a job on an HPC cluster that finished, failed, or was canceled. Includes statistics and information about the properties and results, and tasks for the jobs.
| Column name | Data type | Can be null | Description |
|---|---|---|---|
JobHistoryID |
int |
No |
A unique numeric identifier for a job history entry. A job history entry is created each time a job reaches the finished, failed, or canceled state. For example, one job would correspond to three job history entries if you submit the job and cancel it before it finishes, requeue the job and it fails, and then fix and requeue the job so that it finishes. |
JobID |
int |
No |
The job identifier of the job that was queued and then finished, failed, or was canceled. |
RequeueID |
int |
No |
A numeric identifier for the queuing of the job. Each time a user queues the job, a new RequeueID is assigned for the job. The RequeueID starts at 0 when the user submits a job for the first time, and it is incremented each time the user cancels and requeues the job. |
Name |
nvarchar(80) |
Yes |
The name of the job. |
State |
varchar(8) |
No |
The state for the job. It is one of the following values:
|
EventTime |
datetime |
No |
The date and time in Coordinated Universal Time (UTC) when the job finished, failed, or was canceled. |
SubmitTime |
datetime |
Yes |
The date and time in UTC when the job was submitted. |
StartTime |
datetime |
Yes |
The date and time in UTC when the job started running. If the job is canceled before it starts running, the StartTime is the same as the EventTime. |
Owner |
nvarchar(80) |
No |
The owner of the job. |
Project |
nvarchar(80) |
No |
The project to which the job belongs. |
Template |
nvarchar(50) |
No |
The name of the job template that the job uses. |
Service |
nvarchar(128) |
No |
The name of the service-oriented architecture (SOA) service that the job uses, if the job is a service job. |
KernelCpuTime |
bigint |
No |
The amount of CPU time in milliseconds that the job used while running in privileged or kernel mode. The sum of KernelCpuTime and UserCpuTime is the total CPU time for the job. If the job is canceled before it starts running, the KernelCpuTime is 0. |
UserCpuTime |
bigint |
No |
The amount of CPU time in milliseconds that the job used while running in user mode. The sum of KernelCpuTime and UserCpuTime is the total CPU time for the job. If the job is canceled before it starts running, the UserCpuTime is 0. |
MemoryUsed |
bigint |
No |
The amount of memory in kilobytes that the tasks in the job were using when memory usage for the tasks were most recently sampled, summed over all of the tasks the job. |
NumberOfCalls |
bigint |
No |
The total number of SOA calls that the tasks in the job made. |
CallDuration |
bigint |
No |
The average duration in milliseconds of the SOA calls made by the tasks in the job. |
CallsPerSecond |
bigint |
No |
The average number of SOA calls that the tasks in the job made per second. |
RunTime |
bigint |
No |
The amount of time in milliseconds that all of the tasks in the job took to run. The value of the RunTime column is the sum of the differences between the entries in the EndTime and StartTime columns in the AllocationHistoryView for each of the tasks in the job. |
WaitTime |
bigint |
No |
The amount of time in milliseconds that the job waited in the job queue before the job started to run or was canceled if it never started to run. The value of the WaitTime column is the difference between the values of the StartTime and the SubmitTime columns. When a job is canceled after being queued but before it starts, the value of the StartTime column is the same as the value of the EventTime column. So in this case, the value of the WaitTime column is also the difference between the values of the EventTime and the SubmitTime columns. In this case, the values of the KernelCpuTime and UserCpuTime columns are 0. |
Priority |
varchar(11) |
Yes |
The priority for scheduling the job. The priority can be one of the following values:
The job template that the job uses specifies permissions that affect who can specify elevated priorities. The HPC Job Scheduler Service places jobs with the same priority into the job queue in the order that users submit the jobs, unless a user requeues a job. When a user requeues a job, the HPC Job Scheduler Service places that job first among the jobs with the same priority. |
Type |
varchar(7) |
Yes |
The type of the job. It can be one of the following values:
|
Preemptable |
bit |
Yes |
Indicates whether higher priority jobs could take resources away from this job when it was running. A value of true indicates that higher priority jobs could take resources away from this job when it was running. A value of false indicates that higher priority jobs could not take resources away from this job when it was running. |
NumberOfTasks |
int |
No |
The number of tasks in the job. |
CanceledTasksCount |
int |
No |
The number of tasks that were canceled when the job ran. |
FailedTasksCount |
int |
No |
The number of tasks that failed when the job ran. |
FinishedTasksCount |
int |
No |
The number of tasks that finished when the job ran. |
License |
nvarchar(160) |
Yes |
A list of features for which the job requires licenses, and the number of licenses required for each. The list uses a format of license_name1:number1 [,license_name2:number2…], for example, License1:10,License2:20,License3:12. |
RunUntilCanceled |
bit |
Yes |
Indicates whether the job continues to run and hold resources until the run-time limit expires or someone cancels the job. A value of true indicates that the job continues to run and hold resources until the run-time limit expires or someone cancels the job. A value of false indicates that the job should stop and release its resources when all of the tasks in the job are complete. |
IsExclusive |
bit |
Yes |
Indicates whether the HPC Job Scheduler Service should ensure that no other job runs on the same node while this job runs. A value of true indicates that the HPC Job Scheduler Service should ensure that no other job runs on the same node while this job runs. A value of false indicates that this job can share compute nodes with other jobs. |
FailOnTaskFailure |
bit |
Yes |
Indicates whether the HPC Job Scheduler Service should stop the job and fail the entire job immediately when a task in the job fails. A value of true indicates that the HPC Job Scheduler Service should stop the job and fail the entire job immediately when a task in the job fails. A value of false indicates that the HPC Job Scheduler Service should continue to run the remaining tasks in the job after any task in the job fails. |
CanceledBy |
nvarchar(80) |
Yes |
The user who requested that the job be canceled. |
Remarks
Jobs that are running, queued, or still being configured are not reflected in this view.
The reporting database stores job history information only for the number of days that the DataExtensibilityTtl configuration parameter specifies. This value is 365 by default.
To view the current value of the DataExtensibilityTtl configuration parameter, use the Get-HpcClusterProperty cmdlet with the Parameter and Name parameters, for example:
Get-HpcClusterProperty -Parameter -Name DataExtensibilityTtl
To set or change the value of the DataExtensibilityTtl configuration parameter, use the Set-HpcClusterParameter cmdlet with the DataExtensibilityTtl parameter, for example:
Set-HpcClusterProperty -DataExtensibilityTtl 730
Requirements
Product |
Windows HPC Server 2008 R2 |