Moves a failed, canceled, or queued task to the configuring state so that the task can be queued again when the job is resubmitted.
You can specify the Requeue Task request as follows.
|POST (before HPC Pack 2016)||https://head_node_name:port/WindowsHPC/HPC_cluster_name/Job/job_identifier/Task/task_identifier/Requeue|
|POST (HPC Pack 2016)||https://head_node_name:port/WindowsHPC/Job/job_identifier/Task/task_identifier/Requeue|
For instances of the REST web service that are hosted in Azure, the head node name should have a format of Windows_Azure_service_name.cloudapp.net.
To get the name to use for an HPC cluster that runs at least Microsoft HPC Pack 2008 R2 with Service Pack 3 (SP3), use the Get Clusters operation.
You can specify the following additional parameters on the request URI.
Optional. Specifies the version of the operation to use for this request. To specify Microsoft HPC Pack 2008 R2 with Service Pack 3 (SP3), use a value of 2011-11-01. The minimum version that supports this URI parameter is Microsoft HPC Pack 2008 R2 with SP3.
The value of this URI parameter is ignored if the request also contains the api-version header.
The following table describes required and optional request headers.
Optional. Specifies the version of the operation to use for this request. To specify Microsoft HPC Pack 2008 R2 with SP3, use a value of 2011-11-01. The minimum version that supports this header is Microsoft HPC Pack 2008 R2 with SP3.
The value specified in this header overrides the value specified in the api-version URI parameter if both are specified.
Optional. Specifies the version of the operation to use for this request.
Deprecated beginning with Microsoft HPC Pack 2008 R2 with Service Pack 3 (SP3).
The format of the request body is as follows.
The request XML should include an empty ArrayOfProperty element. If you include other elements as child elements of the ArrayOfProperty element, such as those you use for the Set Task Properties operation, the values of the corresponding properties do not change.
The response includes an HTTP status code and a set of response headers.
A successful operation returns status code 200 (OK). For more information about status codes, see HttpStatusCode.
The error response is dependent upon the api-version used in the request. If the api-version is not provided, or CCP_Version is specifed, then the error response will be an XML string (Note: The error message will vary based on the error):
<string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">Error message text.</string>
If the api-version is 2011-11-01 or later, the error message will be a more descriptive XML response (Note: Values will vary based on the error):
<HpcWebServiceFault xmlns="http://schemas.microsoft.com/HPCS2008R2/common" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <Code>267386880</Code> <Message>Error message text.</Message> <Values i:nil="true" xmlns:a="http://schemas.datacontract.org/2004/07/System.Collections.Generic"/> </HpcWebServiceFault>
The response for this operation includes the following headers.
A comma-separated list of RFC 1918 IP addresses that indicate the sequence of instances of the REST web service that the operation called in order from to right.
Only responses from instances of the REST web service that are hosted on Azure contain this header. Responses from instances of the REST web service that are hosted on premise omit this header.
This header is supported beginning with Microsoft HPC Pack 2008 R2 with SP3 and is not available in previous versions.
The response for this operation also includes standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.
HPC Pack 2008 R2 with at least SP2, or a later version of HPC Pack.